From: Tobias Schramm <tobleminer@gmail.com>
To: qemu-devel@nongnu.org
Cc: aneesh.kumar@linux.vnet.ibm.com, groug@kaod.org,
Tobias Schramm <tobleminer@gmail.com>
Subject: [Qemu-devel] [PATCH v2 0/1] Add fmask/dmask option for 9p mapped mode
Date: Sun, 18 Jun 2017 16:52:57 +0200 [thread overview]
Message-ID: <20170618145258.16231-1-tobleminer@gmail.com> (raw)
Hi,
as suggested by the automated tests I adjusted the code style to be
compatible with QEMUs existing code base.
The previous failed test seems to be irrelevant since it passes fine on my dev
machine and the failure is in a totally unrelated component.
Tobias Schramm
Tobias Schramm (1):
Add support for custom fmasks/dmasks in 9ps mapped mode
fsdev/file-op-9p.h | 4 ++++
fsdev/qemu-fsdev-opts.c | 12 ++++++++++++
hw/9pfs/9p-local.c | 29 +++++++++++++++++++++++++----
hw/9pfs/9p.c | 3 +++
4 files changed, 44 insertions(+), 4 deletions(-)
--
2.13.1
next reply other threads:[~2017-06-18 14:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-18 14:52 Tobias Schramm [this message]
2017-06-18 14:52 ` [Qemu-devel] [PATCH v2 1/1] Add support for custom fmasks/dmasks in 9ps mapped mode Tobias Schramm
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=20170618145258.16231-1-tobleminer@gmail.com \
--to=tobleminer@gmail.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--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).