From: Rusty Russell <rusty@rustcorp.com.au>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: virtualization@lists.linux-foundation.org
Subject: Re: [PATCH 2/3] Virtio draft IV: the block driver
Date: Tue, 24 Jul 2007 13:02:05 +1000 [thread overview]
Message-ID: <1185246125.1803.121.camel@localhost.localdomain> (raw)
In-Reply-To: <200707231313.11847.borntraeger@de.ibm.com>
On Mon, 2007-07-23 at 13:13 +0200, Christian Borntraeger wrote:
> > +#ifdef __KERNEL__
> > +struct gendisk;
> > +struct virtio_device;
> > +
> > +struct gendisk *virtblk_probe(struct virtqueue *vq);
>
> Hello Rusty,
>
> I am currently do some prototyping with virtio IV and found tis small issue in
> the block device. virtblk_probe requires a declaration of virtqueue, not
> virtio_device.
Oops, thanks Christian!
I'll roll this in, thanks!
Rusty.
PS. 2.6.23-rc1 broke the block driver anyway, so will publish new
versions soon.
next prev parent reply other threads:[~2007-07-24 3:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-04 4:12 [PATCH 1/3] Virtio draft IV Rusty Russell
2007-07-04 4:19 ` [PATCH 2/3] Virtio draft IV: the block driver Rusty Russell
2007-07-04 4:40 ` [PATCH 3/3] Virtio draft IV: the net driver Rusty Russell
2007-07-11 10:28 ` Christian Borntraeger
2007-07-11 11:26 ` Rusty Russell
2007-07-11 11:46 ` Christian Borntraeger
2007-07-12 2:23 ` Rusty Russell
2007-07-11 19:27 ` Caitlin Bestler
2007-07-11 10:45 ` Christian Borntraeger
2007-07-11 11:32 ` Rusty Russell
2007-07-11 20:44 ` David Miller
2007-07-12 2:21 ` Rusty Russell
2007-07-12 2:26 ` David Miller
2007-07-05 7:32 ` [PATCH 2/3] Virtio draft IV: the block driver Christian Borntraeger
2007-07-06 0:33 ` Rusty Russell
2007-07-06 0:33 ` Rusty Russell
2007-07-23 11:13 ` Christian Borntraeger
2007-07-24 3:02 ` Rusty Russell [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-09 14:17 Martin Peschke
2007-07-09 15:54 ` Martin Peschke
2007-07-10 4:42 ` Rusty Russell
2007-07-10 12:12 ` Martin Peschke
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=1185246125.1803.121.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=borntraeger@de.ibm.com \
--cc=virtualization@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.