From: "Jan Beulich" <JBeulich@novell.com>
To: "Stephen Rothwell" <sfr@canb.auug.org.au>,
"Benjamin Herrenschmidt" <benh@kernel.crashing.org>
Cc: linuxppc-dev@lists.ozlabs.org,
"H.Peter Anvin" <hpa@linux.intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Arnaud Lacombe <lacombar@gmail.com>
Subject: Re: linux-next: build warning in Linus' tree
Date: Thu, 18 Nov 2010 07:45:21 +0000 [thread overview]
Message-ID: <4CE4E7A10200007800022F33@vpn.id2.novell.com> (raw)
In-Reply-To: <1290052544.32570.1.camel@pasglop>
>>> On 18.11.10 at 04:55, Benjamin Herrenschmidt <benh@kernel.crashing.org>=
wrote:
> On Mon, 2010-10-25 at 17:03 +1100, Stephen Rothwell wrote:
>> Hi Arnaud,
>>=20
>> On Sun, 24 Oct 2010 23:47:09 -0400 Arnaud Lacombe <lacombar@gmail.com> =
wrote:
>> >
>> > The following patch should fix this warning.
>>=20
>> I think the following is preferable. Not tested yet, I will test
>> tomorrow and submit properly then.
>=20
> I agree. Tho I don't understand the original problem. Both definitions
> have no parenthesis for me and I don't see warnings, or am I missing
> some changes still in -next that cause this ?
There had been parentheses for a short while, but them causing
problems for at least one other arch, they got removed again.
Jan
prev parent reply other threads:[~2010-11-18 8:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20101025135237.337b8321.sfr@canb.auug.org.au>
2010-10-25 3:47 ` linux-next: build warning in Linus' tree Arnaud Lacombe
2010-10-25 6:03 ` Stephen Rothwell
2010-11-18 3:55 ` Benjamin Herrenschmidt
2010-11-18 4:47 ` Arnaud Lacombe
2010-11-18 7:45 ` Jan Beulich [this message]
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=4CE4E7A10200007800022F33@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=benh@kernel.crashing.org \
--cc=hpa@linux.intel.com \
--cc=lacombar@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).