From: Andrew Morton <akpm@linux-foundation.org>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: linux-kernel@vger.kernel.org, arjan@infradead.org,
arjan@linux.intel.com, mingo@elte.hu
Subject: Re: + fix-fastboot-make-the-raid-autodetect-code-wait-for-all-devices-to-init.patch added to -mm tree
Date: Thu, 4 Sep 2008 10:36:46 -0700 [thread overview]
Message-ID: <20080904103646.1826d797.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0809040941550.19666@shark.he.net>
On Thu, 4 Sep 2008 09:45:10 -0700 (PDT) "Randy.Dunlap" <rdunlap@xenotime.net> wrote:
> On Wed, 3 Sep 2008, akpm@linux-foundation.org wrote:
>
> > Subject: fix "fastboot: make the raid autodetect code wait for all devices to init"
> > From: Andrew Morton <akpm@linux-foundation.org>
> >
> > : commit b52c36a95ed8026b6925fe8595ebcab6921ae62d
> > : Author: Arjan van de Ven <arjan@linux.intel.com>
> > : Date: Sun Jul 20 13:07:09 2008 -0700
> > :
> > : fastboot: make the raid autodetect code wait for all devices to init
> >
> > init/do_mounts_md.c: In function `md_run_setup':
> > init/do_mounts_md.c:282: warning: ISO C90 forbids mixed declarations and code
> >
> > How did this happen?
>
> There are so many warnings that they get lost in the noise
> unless someone is actively looking for them.
Well if that's the explanation then OK (sort-of). I'm more concerned
that the warning does not appear *at all* for some people's
compiler/Kconfig combinations.
next prev parent reply other threads:[~2008-09-04 17:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200809040539.m845dEgX022904@imap1.linux-foundation.org>
2008-09-04 16:45 ` + fix-fastboot-make-the-raid-autodetect-code-wait-for-all-devices-to-init.patch added to -mm tree Randy.Dunlap
2008-09-04 17:36 ` Andrew Morton [this message]
2008-09-04 17:38 ` Arjan van de Ven
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=20080904103646.1826d797.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rdunlap@xenotime.net \
/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