From: Rusty Russell <rusty@rustcorp.com.au>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
john cooper <john.cooper@redhat.com>
Subject: Re: linux-next: Tree for April 1 (virtio_blk warning)
Date: Tue, 6 Apr 2010 12:10:48 +0930 [thread overview]
Message-ID: <201004061210.48840.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20100401091312.85775242.randy.dunlap@oracle.com>
On Fri, 2 Apr 2010 02:43:12 am Randy Dunlap wrote:
> On Thu, 1 Apr 2010 17:23:17 +1100 Stephen Rothwell wrote:
>
> > Hi all,
> >
> > Changes since 20100331:
>
>
> drivers/block/virtio_blk.c:228:13: warning: multi-character character constant
>
> due to:
>
> if (cmd == 'VBID') {
John? That looks suspiciously like untested code.
Thanks,
Rusty.
next prev parent reply other threads:[~2010-04-06 2:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 6:23 linux-next: Tree for April 1 Stephen Rothwell
2010-04-01 16:13 ` linux-next: Tree for April 1 (virtio_blk warning) Randy Dunlap
2010-04-06 2:40 ` Rusty Russell [this message]
2010-04-06 18:15 ` john cooper
2010-04-06 20:58 ` Randy Dunlap
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=201004061210.48840.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=john.cooper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
/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