From: Peter Maydell <peter.maydell@linaro.org>
To: An-Cheng Huang <ancheng@ubnt.com>
Cc: riku.voipio@iki.fi, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3/3] linux-user: Implement setxattr/getxattr/removexattr syscalls
Date: Thu, 1 Sep 2011 17:08:55 +0100 [thread overview]
Message-ID: <CAFEAcA8CPTQhK1fniFROpse0AKowcwkJzp8=2GZrNa9NJw3fJA@mail.gmail.com> (raw)
In-Reply-To: <20110809193406.GD24592@debian.localdomain>
On 9 August 2011 20:34, An-Cheng Huang <ancheng@ubnt.com> wrote:
> This patch implements the setxattr, getxattr, and removexattr syscalls
> if CONFIG_ATTR is enabled.
>
> Note that since libattr uses indirect syscalls for these, this change
> depends on the fix for indirect syscall handling on MIPS.
>
> Signed-off-by: An-Cheng Huang <ancheng@ubnt.com>
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
prev parent reply other threads:[~2011-09-01 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-09 19:34 [Qemu-devel] [PATCH 3/3] linux-user: Implement setxattr/getxattr/removexattr syscalls An-Cheng Huang
2011-09-01 16:08 ` 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='CAFEAcA8CPTQhK1fniFROpse0AKowcwkJzp8=2GZrNa9NJw3fJA@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=ancheng@ubnt.com \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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).