Message ID | 20250305-fixed-type-genmasks-v4-1-1873dcdf6723@wanadoo.fr (mailing list archive) |
---|---|
State | New |
Headers | show |
Series | bits: Fixed-type GENMASK()/BIT() | expand |
Hi Vincent! On Wed, Mar 05, 2025 at 10:00:13PM +0900, Vincent Mailhol via B4 Relay wrote: > From: Vincent Mailhol <mailhol.vincent@wanadoo.fr> > > "int" was misspelled as "init" in GENMASK_U128() comments. Fix the typo. > > Signed-off-by: Vincent Mailhol <mailhol.vincent@wanadoo.fr> Thanks for respinning the series. I'll take this fix in bitmap-for-next, so if you need v2, you'll not have to bear this thing too. Thanks, Yury > --- > include/linux/bits.h | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/include/linux/bits.h b/include/linux/bits.h > index 61a75d3f294bfa96267383b5e2fd2a5d4593fcee..14fd0ca9a6cd17339dd2f69e449558312a8a001b 100644 > --- a/include/linux/bits.h > +++ b/include/linux/bits.h > @@ -40,7 +40,7 @@ > * Missing asm support > * > * __GENMASK_U128() depends on _BIT128() which would not work > - * in the asm code, as it shifts an 'unsigned __init128' data > + * in the asm code, as it shifts an 'unsigned __int128' data > * type instead of direct representation of 128 bit constants > * such as long and unsigned long. The fundamental problem is > * that a 128 bit constant will get silently truncated by the > > -- > 2.45.3 >
On Wed, Mar 05, 2025 at 10:00:13PM +0900, Vincent Mailhol via B4 Relay wrote: > From: Vincent Mailhol <mailhol.vincent@wanadoo.fr> > > "int" was misspelled as "init" in GENMASK_U128() comments. Fix the typo. Please, fix it everywhere: $ git grep -lw __init128 include/linux/bits.h include/uapi/linux/const.h tools/include/linux/bits.h tools/include/uapi/linux/const.h
On Wed, Mar 05, 2025 at 09:30:20AM -0500, Yury Norov wrote: > On Wed, Mar 05, 2025 at 10:00:13PM +0900, Vincent Mailhol via B4 Relay wrote: > > From: Vincent Mailhol <mailhol.vincent@wanadoo.fr> > > > > "int" was misspelled as "init" in GENMASK_U128() comments. Fix the typo. > > Thanks for respinning the series. I'll take this fix in bitmap-for-next, so > if you need v2, you'll not have to bear this thing too. Before doing that, please read my comment first.
On Wed, Mar 05, 2025 at 04:36:12PM +0200, Andy Shevchenko wrote: > On Wed, Mar 05, 2025 at 09:30:20AM -0500, Yury Norov wrote: > > On Wed, Mar 05, 2025 at 10:00:13PM +0900, Vincent Mailhol via B4 Relay wrote: > > > From: Vincent Mailhol <mailhol.vincent@wanadoo.fr> > > > > > > "int" was misspelled as "init" in GENMASK_U128() comments. Fix the typo. > > > > Thanks for respinning the series. I'll take this fix in bitmap-for-next, so > > if you need v2, you'll not have to bear this thing too. > > Before doing that, please read my comment first. Already did. Yes, you're right. Vincent, can you send the fix separately, so I'll move it in the upcoming merge window?
On 05/03/2025 at 23:38, Yury Norov wrote: > On Wed, Mar 05, 2025 at 04:36:12PM +0200, Andy Shevchenko wrote: >> On Wed, Mar 05, 2025 at 09:30:20AM -0500, Yury Norov wrote: >>> On Wed, Mar 05, 2025 at 10:00:13PM +0900, Vincent Mailhol via B4 Relay wrote: >>>> From: Vincent Mailhol <mailhol.vincent@wanadoo.fr> >>>> >>>> "int" was misspelled as "init" in GENMASK_U128() comments. Fix the typo. >>> >>> Thanks for respinning the series. I'll take this fix in bitmap-for-next, so >>> if you need v2, you'll not have to bear this thing too. >> >> Before doing that, please read my comment first. > > Already did. Yes, you're right. > > Vincent, can you send the fix separately, so I'll move it in the > upcoming merge window? Here it is: https://lore.kernel.org/all/20250305-fix_init128_typo-v1-1-cbe5b8e54e7d@wanadoo.fr/ As requested, I will exclude this from the v5. Yours sincerely, Vincent Mailhol
diff --git a/include/linux/bits.h b/include/linux/bits.h index 61a75d3f294bfa96267383b5e2fd2a5d4593fcee..14fd0ca9a6cd17339dd2f69e449558312a8a001b 100644 --- a/include/linux/bits.h +++ b/include/linux/bits.h @@ -40,7 +40,7 @@ * Missing asm support * * __GENMASK_U128() depends on _BIT128() which would not work - * in the asm code, as it shifts an 'unsigned __init128' data + * in the asm code, as it shifts an 'unsigned __int128' data * type instead of direct representation of 128 bit constants * such as long and unsigned long. The fundamental problem is * that a 128 bit constant will get silently truncated by the