From: "Michael S. Tsirkin" <mst@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Greg Kurz <groug@kaod.org>, P J P <ppandit@redhat.com>,
Qemu Developers <qemu-devel@nongnu.org>,
Prasad J Pandit <pjp@fedoraproject.org>,
Felix Wilhelm <fwilhelm@ernw.de>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH] 9pfs: add check for relative path
Date: Mon, 22 Aug 2016 18:02:55 +0300 [thread overview]
Message-ID: <20160822175343-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAFEAcA9sb=XhfJ0C=DP8+NCJ9JTNmyq8fEfKkqMj=YTd_b0BDA@mail.gmail.com>
On Mon, Aug 22, 2016 at 10:23:19AM +0100, Peter Maydell wrote:
> On 19 August 2016 at 18:30, Greg Kurz <groug@kaod.org> wrote:
> > Maybe the check can even be made in the top layer then. I should spend
> > more time to see which is best.
> >
> > My main concern now is that, unlike I said on IRC, I'm afraid I won't be
> > able to work on this before next Wednesday... :-\
> >
> > Hope it is not too late for 2.7...
>
> Opinions welcome on whether we need to hold 2.7 for this bug.
>
> thanks
> -- PMM
Not really sure, but balloon migration seems borken too,
and I'm trying to fix it up.
--
MST
next prev parent reply other threads:[~2016-08-22 15:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 5:13 [Qemu-devel] [PATCH] 9pfs: add check for relative path P J P
2016-08-11 6:17 ` no-reply
2016-08-11 6:27 ` Fam Zheng
2016-08-18 16:55 ` Greg Kurz
2016-08-11 6:31 ` Aneesh Kumar K.V
2016-08-18 15:19 ` Greg Kurz
2016-08-18 17:06 ` Greg Kurz
2016-08-19 14:55 ` Peter Maydell
2016-08-19 15:14 ` Peter Maydell
2016-08-19 16:37 ` Greg Kurz
2016-08-19 17:03 ` Peter Maydell
2016-08-19 17:30 ` Greg Kurz
2016-08-22 9:23 ` Peter Maydell
2016-08-22 10:07 ` P J P
2016-08-22 15:02 ` Michael S. Tsirkin [this message]
2016-08-22 15:07 ` Peter Maydell
2016-08-22 14:14 ` Michael S. Tsirkin
2016-08-19 16:24 ` Greg Kurz
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=20160822175343-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=fwilhelm@ernw.de \
--cc=groug@kaod.org \
--cc=peter.maydell@linaro.org \
--cc=pjp@fedoraproject.org \
--cc=ppandit@redhat.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 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.