[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.02.1511060743560.2054@localhost6.localdomain6>
Date: Fri, 6 Nov 2015 07:44:18 +0100 (CET)
From: Julia Lawall <julia.lawall@...6.fr>
To: Julian Calaby <julian.calaby@...il.com>
cc: Linus Torvalds <torvalds@...ux-foundation.org>,
David Miller <davem@...emloft.net>,
Andrew Morton <akpm@...ux-foundation.org>,
sparclinux <sparclinux@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
kernel-janitors@...r.kernel.org
Subject: Re: [GIT] Sparc
On Fri, 6 Nov 2015, Julian Calaby wrote:
> Hi Linus,
>
> On Fri, Nov 6, 2015 at 11:56 AM, Linus Torvalds
> <torvalds@...ux-foundation.org> wrote:
> > On Thu, Nov 5, 2015 at 4:43 PM, Linus Torvalds
> > <torvalds@...ux-foundation.org> wrote:
> >>
> >> Not that this *matters*, but it's a bit odd to have to cast constants
> >> to perfectly regular C types.
> >
> > Looking around with "git grep", there's a few more of these.
> >
> > - btrfs seems to like "(unsigned long)-1"
> >
> > There's a few other users of that too, including more sparc uses.
> >
> > - scsi/qla seems to like "(unsigned long)<hexnumber>"
> >
> > - fmdrv_common.h seems to like "((unsigned long)1<<x)" for bitmaps
> >
> > along with a smattering of random noise all over of "(unsigned long)
> > n" where 'n' is some integer.
> >
> > Apparently people aren't as aware of the normal "ul" postfix syntax as
> > I would have expected. That said, it's a hundred-odd cases in all of
> > the kernel, so it's still fairly rare.
>
> Maybe this is something the kernel-janitors team should look at? (CC'd)
Do you have some concrete examples of the code that is undesirable?
thanks,
julia
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists