From: Richard Henderson <rth@twiddle.net>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
QEMU-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] e1000: Do reset when E1000_CTRL_RST bit is set.
Date: Fri, 05 Aug 2011 11:34:41 -0700 [thread overview]
Message-ID: <4E3C37C1.6080207@twiddle.net> (raw)
In-Reply-To: <4E3C1FFF.8070409@codemonkey.ws>
On 08/05/2011 09:53 AM, Anthony Liguori wrote:
>> + if (val& E1000_CTRL_RST) {
>
> You'll break some GCCs with -Wall -Werror with this. Please do:
>
> if ((val & E1000_CTRL_RST)) {
Err, really? What versions?
I don't recall that ever being true.
r~
next prev parent reply other threads:[~2011-08-05 18:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 14:36 [Qemu-devel] [PATCH] e1000: Do reset when E1000_CTRL_RST bit is set Anthony PERARD
2011-08-05 16:53 ` Anthony Liguori
2011-08-05 18:34 ` Richard Henderson [this message]
2011-08-05 18:44 ` Peter Maydell
2011-08-09 14:10 ` Anthony PERARD
2011-08-09 17:10 ` Peter Maydell
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=4E3C37C1.6080207@twiddle.net \
--to=rth@twiddle.net \
--cc=anthony.perard@citrix.com \
--cc=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.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).