qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Greg Kurz <groug@kaod.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 0/8] 9pfs patches for 2.10 20170629
Date: Thu, 29 Jun 2017 17:00:51 +0100	[thread overview]
Message-ID: <CAFEAcA_nEPOV25nimO1w2K51G7ooaRUseSwwy=Vc-gvFv2AkTA@mail.gmail.com> (raw)
In-Reply-To: <1498743831-28676-1-git-send-email-groug@kaod.org>

On 29 June 2017 at 14:43, Greg Kurz <groug@kaod.org> wrote:
> The following changes since commit 464588675455afda2899e20a0b120e4075de50c7:
>
>   Merge remote-tracking branch 'remotes/sstabellini/tags/xen-20170627-tag' into staging (2017-06-29 11:45:01 +0100)
>
> are available in the git repository at:
>
>   https://github.com/gkurz/qemu.git tags/for-upstream
>
> for you to fetch changes up to 06a37db7b12e4d42a6699c2fef820158f470ec4f:
>
>   9pfs: handle transport errors in pdu_complete() (2017-06-29 15:11:51 +0200)
>
> ----------------------------------------------------------------
> - fixes a minor bug that could possibly prevent old guests to remove
>   directories
> - makes default permissions for new files configurable from the cmdline
>   when using mapped security modes
> - handle transport errors
> - g_malloc()+memcpy() converted to g_memdup()
>
> ----------------------------------------------------------------
> Bruce Rogers (1):
>       9pfs: local: remove: use correct path component
>
> Greg Kurz (4):
>       virtio-9p: record element after sanity checks
>       virtio-9p: message header is 7-byte long
>       virtio-9p: break device if buffers are misconfigured
>       9pfs: handle transport errors in pdu_complete()
>
> Marc-André Lureau (1):
>       9pfs: replace g_malloc()+memcpy() with g_memdup()
>
> Stefano Stabellini (1):
>       xen-9pfs: disconnect if buffers are misconfigured
>
> Tobias Schramm (1):
>       9pfs: local: Add support for custom fmode/dmode in 9ps mapped security modes
>

Applied, thanks.

-- PMM

  parent reply	other threads:[~2017-06-29 16:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-29 13:43 [Qemu-devel] [PULL 0/8] 9pfs patches for 2.10 20170629 Greg Kurz
2017-06-29 13:43 ` [Qemu-devel] [PULL 1/8] 9pfs: local: remove: use correct path component Greg Kurz
2017-06-29 13:43 ` [Qemu-devel] [PULL 2/8] 9pfs: local: Add support for custom fmode/dmode in 9ps mapped security modes Greg Kurz
2017-06-29 13:43 ` [Qemu-devel] [PULL 3/8] 9pfs: replace g_malloc()+memcpy() with g_memdup() Greg Kurz
2017-06-29 13:43 ` [Qemu-devel] [PULL 4/8] virtio-9p: record element after sanity checks Greg Kurz
2017-06-29 13:43 ` [Qemu-devel] [PULL 5/8] virtio-9p: message header is 7-byte long Greg Kurz
2017-06-29 13:43 ` [Qemu-devel] [PULL 6/8] virtio-9p: break device if buffers are misconfigured Greg Kurz
2017-06-29 13:43 ` [Qemu-devel] [PULL 7/8] xen-9pfs: disconnect " Greg Kurz
2017-06-29 13:43 ` [Qemu-devel] [PULL 8/8] 9pfs: handle transport errors in pdu_complete() Greg Kurz
2017-06-29 16:00 ` Peter Maydell [this message]
2017-06-29 16:59   ` [Qemu-devel] [PULL 0/8] 9pfs patches for 2.10 20170629 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='CAFEAcA_nEPOV25nimO1w2K51G7ooaRUseSwwy=Vc-gvFv2AkTA@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=groug@kaod.org \
    --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).