From: Ralf Baechle <ralf@linux-mips.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Wu Zhangjin <wuzhangjin@gmail.com>, Arnd Bergmann <arnd@arndb.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Remis Lima Baima <remis.developer@googlemail.com>,
Christoph Hellwig <hch@lst.de>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [PATCH] kernel/time/tick-sched.c: fix warning of printk's argument format
Date: Fri, 9 Oct 2009 12:28:14 +0200 [thread overview]
Message-ID: <20091009102814.GA619@linux-mips.org> (raw)
In-Reply-To: <alpine.LFD.2.01.0910080755390.3432@localhost.localdomain>
On Thu, Oct 08, 2009 at 08:03:40AM -0700, Linus Torvalds wrote:
> > This patch will fix the following warning:
>
> No it won't. It will add a lot of new warnings.
>
> The thing is, almost all architectures (including x86) have
>
> unsigned int __softirq_pending;
>
> but then in <asm-generic/hardirq.h> we have
>
> unsigned long __softirq_pending;
>
> for some unfathomable reason. Quite frankly, I think Arnd just screwed up
> the "generic" version, and the fix is almost certainly to just make the
> generic version match all the main architectures.
>
> I don't have any architectures using the generic header file, though, so
> I'm not going to do that change blindly. People who do should look at it
> (alpha, powerpc and mips look like the only ones that might be 64-bit, but
> I didn't check very carefully - just grepped for it)
>
> Added Cc's for some people that have worked on, or used, that generic
> header file. Is there any possible reason why it is "unsigned long" in
> that one?
I think for no other reason than many other bitfields in kernel being
unsigned long or arrays of unsigned long. Except of course that
__softirq_pending is never being used with the <asm/bitops.h> operations
that operate on unsigned longs.
Patch in followup email.
Ralf
next prev parent reply other threads:[~2009-10-09 10:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-08 14:46 [PATCH] kernel/time/tick-sched.c: fix warning of printk's argument format Wu Zhangjin
2009-10-08 15:03 ` Linus Torvalds
2009-10-08 15:31 ` Wu Zhangjin
2009-10-09 6:56 ` Yong Zhang
2009-10-09 10:28 ` Ralf Baechle [this message]
2009-10-09 10:41 ` [PATCH] IRQ: Change __softirq_pending to unsigned int in asm-generic/hardirq.h Ralf Baechle
[not found] ` <200910091542.29457.arnd@arndb.de>
2009-10-09 21:41 ` [PATCH] kernel/time/tick-sched.c: fix warning of printk's argument format Helge Deller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091009102814.GA619@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=remis.developer@googlemail.com \
--cc=torvalds@linux-foundation.org \
--cc=wuzhangjin@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox