From: Peter Maydell <peter.maydell@linaro.org>
To: Christian Schoenebeck <qemu_oss@crudebyte.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>, Greg Kurz <groug@kaod.org>
Subject: Re: [PULL 0/4] 9p queue for 5.2 (2020-11-06)
Date: Fri, 6 Nov 2020 10:34:12 +0000 [thread overview]
Message-ID: <CAFEAcA_aaWxPfupDTrkoPSZoHEyaGhP374rx=8Ei+DJYdZvs=g@mail.gmail.com> (raw)
In-Reply-To: <cover.1604653990.git.qemu_oss@crudebyte.com>
On Fri, 6 Nov 2020 at 09:36, Christian Schoenebeck
<qemu_oss@crudebyte.com> wrote:
>
> The following changes since commit e2766868d45d8c8f8991cfd133e6a0c14abfe577:
>
> Merge remote-tracking branch 'remotes/kraxel/tags/fixes-20201104-pull-request' into staging (2020-11-04 22:13:02 +0000)
>
> are available in the Git repository at:
>
> https://github.com/cschoenebeck/qemu.git tags/pull-9p-20201106
>
> for you to fetch changes up to e6b99460b14469e0b83febc8d5a501947d1d5c7c:
>
> hw/9pfs: Fix Kconfig dependency problem between 9pfs and Xen (2020-11-05 15:21:11 +0100)
>
> ----------------------------------------------------------------
> 9pfs: some fixes
>
> * Fix meson build config for Xen.
>
> * Code style fixes.
Applied, thanks.
Please update the changelog at https://wiki.qemu.org/ChangeLog/5.2
for any user-visible changes.
-- PMM
prev parent reply other threads:[~2020-11-06 10:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 9:13 [PULL 0/4] 9p queue for 5.2 (2020-11-06) Christian Schoenebeck
2020-11-06 9:13 ` [PULL 2/4] hw/9pfs : open brace '{' following struct go on the same line Christian Schoenebeck
2020-11-06 9:13 ` [PULL 3/4] hw/9pfs : add space before the open parenthesis '(' Christian Schoenebeck
2020-11-06 9:13 ` [PULL 4/4] hw/9pfs: Fix Kconfig dependency problem between 9pfs and Xen Christian Schoenebeck
2020-11-06 9:13 ` [PULL 1/4] hw/9pfs : add spaces around operator Christian Schoenebeck
2020-11-06 10:34 ` Peter Maydell [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='CAFEAcA_aaWxPfupDTrkoPSZoHEyaGhP374rx=8Ei+DJYdZvs=g@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=groug@kaod.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu_oss@crudebyte.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).