From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL] Virtfs update
Date: Wed, 02 Nov 2011 19:39:47 +0530 [thread overview]
Message-ID: <8739e6haz8.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <4EB13AA8.5080704@us.ibm.com>
On Wed, 02 Nov 2011 07:42:16 -0500, Anthony Liguori <aliguori@us.ibm.com> wrote:
> On 11/02/2011 05:22 AM, Aneesh Kumar K.V wrote:
> >
> > The following changes since commit e072ea2fd8fdceef64159b9596d3c15ce01bea91:
> >
> > Bump version to 1.0-rc0 (2011-11-01 19:37:01 -0500)
> >
> > are available in the git repository at:
> > git://repo.or.cz/qemu/v9fs.git for-upstream-8
> >
> > Aneesh Kumar K.V (1):
> > hw/9pfs: Move opt validation to FsDriver callback
> >
> > Stefan Hajnoczi (1):
> > hw/9pfs: use g_vasprintf() instead of rolling our own
>
> Neither of these look like bug fixes to me.
>
> Regards,
>
The related discussion for the first commit can be found at
http://article.gmane.org/gmane.comp.emulators.qemu/122891
I dropped the second commit. updated details below.
The following changes since commit e072ea2fd8fdceef64159b9596d3c15ce01bea91:
Bump version to 1.0-rc0 (2011-11-01 19:37:01 -0500)
are available in the git repository at:
git://repo.or.cz/qemu/v9fs.git for-upstream-8
Stefan Hajnoczi (1):
hw/9pfs: use g_vasprintf() instead of rolling our own
hw/9pfs/virtio-9p.c | 103 ++-------------------------------------------------
1 files changed, 4 insertions(+), 99 deletions(-)
next prev parent reply other threads:[~2011-11-02 14:11 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 10:22 [Qemu-devel] [PULL] Virtfs update Aneesh Kumar K.V
2011-11-02 12:42 ` Anthony Liguori
2011-11-02 14:09 ` Aneesh Kumar K.V [this message]
2011-11-03 13:09 ` Anthony Liguori
2011-11-02 15:55 ` Markus Armbruster
-- strict thread matches above, loose matches on Subject: below --
2015-06-16 15:29 [Qemu-devel] [PULL] VirtFS update Aneesh Kumar K.V
2015-06-17 11:26 ` Peter Maydell
2015-03-16 10:09 Aneesh Kumar K.V
2015-03-16 13:55 ` Peter Maydell
2014-09-04 16:01 Aneesh Kumar K.V
2014-09-04 18:21 ` Peter Maydell
2014-03-07 15:16 Aneesh Kumar K.V
2014-03-08 12:52 ` Peter Maydell
2014-02-05 7:14 Aneesh Kumar K.V
2014-02-05 7:58 ` Aneesh Kumar K.V
2014-02-10 18:48 ` Peter Maydell
2014-02-10 19:21 ` Andreas Färber
2014-02-10 19:43 ` Peter Maydell
2014-02-10 19:48 ` Andreas Färber
2014-02-10 19:51 ` Peter Maydell
2013-05-29 11:33 Aneesh Kumar K.V
2013-05-31 18:48 ` Anthony Liguori
2012-12-05 16:37 Aneesh Kumar K.V
2012-12-10 16:58 ` Anthony Liguori
2012-07-31 17:27 Aneesh Kumar K.V
2012-08-03 20:45 ` Anthony Liguori
2012-02-26 17:44 Aneesh Kumar K.V
2012-02-28 15:33 ` Anthony Liguori
2012-01-30 16:14 Aneesh Kumar K.V
2012-02-07 12:36 ` Aneesh Kumar K.V
2012-01-23 13:02 Aneesh Kumar K.V
2012-01-23 17:05 ` Anthony Liguori
2012-01-23 18:25 ` Aneesh Kumar K.V
2011-12-21 7:57 Aneesh Kumar K.V
2011-12-27 16:36 ` Anthony Liguori
2011-12-17 13:31 Aneesh Kumar K.V
2011-12-05 9:04 Aneesh Kumar K.V
2011-09-27 9:11 Aneesh Kumar K.V
2011-09-29 20:05 ` Anthony Liguori
2011-09-13 13:27 Aneesh Kumar K.V
2011-09-15 19:10 ` Anthony Liguori
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=8739e6haz8.fsf@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=aliguori@us.ibm.com \
--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).