From: Greg Kurz <groug@kaod.org>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>, Greg Kurz <groug@kaod.org>
Subject: [Qemu-devel] [PULL 0/1] 9p patches for 2.13 20180502
Date: Wed, 2 May 2018 13:13:17 +0200 [thread overview]
Message-ID: <20180502111318.129888-1-groug@kaod.org> (raw)
The following changes since commit 26bd8d98c4b3284a4c6fe3b67c98b1edd00e9beb:
Merge remote-tracking branch 'remotes/vivier/tags/m68k-for-2.13-pull-request' into staging (2018-05-01 15:26:06 +0100)
are available in the Git repository at:
https://github.com/gkurz/qemu.git tags/for-upstream
for you to fetch changes up to 8f9c64bfa584ab66b8bcbfc162efa179f7f1cd41:
9p: add trace event for v9fs_setattr() (2018-05-02 08:59:24 +0200)
----------------------------------------------------------------
Just one trace
----------------------------------------------------------------
Greg Kurz (1):
9p: add trace event for v9fs_setattr()
hw/9pfs/9p.c | 5 +++++
hw/9pfs/trace-events | 2 ++
2 files changed, 7 insertions(+)
--
2.14.3
next reply other threads:[~2018-05-02 11:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-02 11:13 Greg Kurz [this message]
2018-05-02 11:13 ` [Qemu-devel] [PULL 1/1] 9p: add trace event for v9fs_setattr() Greg Kurz
2018-05-03 10:25 ` [Qemu-devel] [PULL 0/1] 9p patches for 2.13 20180502 Peter Maydell
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=20180502111318.129888-1-groug@kaod.org \
--to=groug@kaod.org \
--cc=peter.maydell@linaro.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).