From: Greg Kurz <groug@kaod.org>
To: Michael Roth <mdroth@linux.vnet.ibm.com>
Cc: Thomas Huth <thuth@redhat.com>,
qemu-devel@nongnu.org, qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] virtfs: error out gracefully when mandatory suboptions are missing
Date: Tue, 5 Sep 2017 19:00:10 +0200 [thread overview]
Message-ID: <20170905190010.0c84335f@bahia> (raw)
In-Reply-To: <150462482278.16876.9815938798442180307@loki>
[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]
On Tue, 05 Sep 2017 10:20:22 -0500
Michael Roth <mdroth@linux.vnet.ibm.com> wrote:
[...]
> >
> > Well, it's been there forever and it isn't a critical fix... but the
> > thread on qemu-discuss the other day showed that it was confusing
> > people, and the fix is trivial. So I guess it doesn't hurt to have
> > this in stable. :)
> >
> > Michael,
> >
> > I'll send a pull req later today. If it's not too late, maybe you can add
> > this patch to 2.9.1 when it's merged in master?
>
> We're in freeze as of yesterday with release set for Thursday, so it's a
> bit late. OTOH I don't have test coverage for virtfs and the patch seems
> isolated enough that I don't see any harm in slipping it in if it
> lands in master by tomorrow. Otherwise it'll have to wait for 2.10.1,
> which I'm hoping to get out this month.
>
The fix just got merged.
commit 32b6943699948f7adc35ada233fbd25daffad5e9
Author: Greg Kurz <groug@kaod.org>
Date: Mon Sep 4 09:59:01 2017 +0200
virtfs: error out gracefully when mandatory suboptions are missing
Cheers,
--
Greg
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2017-09-05 17:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-04 7:59 [Qemu-devel] [PATCH] virtfs: error out gracefully when mandatory suboptions are missing Greg Kurz
2017-09-05 11:50 ` Thomas Huth
2017-09-05 13:35 ` Thomas Huth
2017-09-05 14:24 ` Greg Kurz
2017-09-05 15:20 ` Michael Roth
2017-09-05 17:00 ` Greg Kurz [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=20170905190010.0c84335f@bahia \
--to=groug@kaod.org \
--cc=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=thuth@redhat.com \
/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).