From: Randy Dunlap <randy.dunlap@oracle.com>
To: john cooper <john.cooper@redhat.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Randy Dunlap <randy.dunlap@oracle.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Marc Haber <mh+qemu-devel@zugschlus.de>
Subject: Re: linux-next: Tree for April 1 (virtio_blk warning)
Date: Tue, 6 Apr 2010 13:58:59 -0700 [thread overview]
Message-ID: <20100406135859.ed1fa4c4.randy.dunlap@oracle.com> (raw)
In-Reply-To: <4BBB7A44.2020300@redhat.com>
On Tue, 06 Apr 2010 14:15:32 -0400 john cooper wrote:
> Rusty Russell wrote:
> > 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.
>
> It does work as advertised although gcc is obliged to squawk
> at multi-byte character constants due to portability concerns.
Thanks. I wasn't aware of that gcc extension.
> Note I'd intended that only as an example for the benefit of
> completeness in the associated patch set, and to stick out
> like a sore thumb of sorts. Marc Haber had suggested exposing
> the id string to the guest userland via /sys which is what I
> had expected to displace the loose ioctl example above. In
> fact that discussion is what prodded revisiting this issue in
> the first place.
>
> Unsure whether Marc (cc'ed here) is still planning to pursue
> that interface so unless I hear something to the contrary in
> the next day or so I'll package up a suitable ioctl interface
> and forward a patch. It doesn't hurt to provide ioctl access
> to the info in addition to exposing it via /sys, but I'd
> hoped the latter would overshadow the need to do so.
---
~Randy
prev parent reply other threads:[~2010-04-06 21:00 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
2010-04-06 18:15 ` john cooper
2010-04-06 20:58 ` Randy Dunlap [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=20100406135859.ed1fa4c4.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=john.cooper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mh+qemu-devel@zugschlus.de \
--cc=rusty@rustcorp.com.au \
--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;
as well as URLs for NNTP newsgroup(s).