From: Riku Voipio <riku.voipio@iki.fi>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
Riku Voipio <riku.voipio@iki.fi>,
Chen Gang S <gang.chen@sunrus.com.cn>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] linux-user/syscall.c: Let all lock_user_struct() and unlock_user_struct() paired with each other
Date: Wed, 28 Jan 2015 16:27:05 +0200 [thread overview]
Message-ID: <20150128142705.GA22971@afflict.kos.to> (raw)
In-Reply-To: <CAFEAcA8q7jNqL8DFygnHaiiv=2pGKXBQ_Gi1icOn9H=diOXK5Q@mail.gmail.com>
Hi,
First of all, thanks Chen for taking time to improve the linux-user
codebase in qemu!
On Mon, Jan 26, 2015 at 03:01:52PM +0000, Peter Maydell wrote:
> On 26 January 2015 at 14:59, Chen Gang S <gang.chen@sunrus.com.cn> wrote:
> > On 1/26/15 06:10, Peter Maydell wrote:
> >> I would just like the commit message to be clear about the
> >> scope of the work the patch covers. If the patch is just "Fix
> >> mismatched lock/unlock calls in IPC struct conversion functions"
> >> then that's fine, but the commit message should say that. At the
> >> moment the commit message is very vague.
> >>
> >
> > OK, thanks.
> >
> > I am not quite familiar with this file, so I describe the modification
> > by function name, e.g. lock_user_struct() and unlick_user_struct() in
> > the patch subject.
> In a big file I think it's often more useful to describe the
> functions which are being changed. My suggested subject would be:
> "Fix mismatched lock/unlock calls in IPC struct conversion functions"
> Riku can decide if he wants a v2 or will just fix it up as he
> applies it to his linux-user tree.
No need for v2, I've change the title in my tree.
Riku
next prev parent reply other threads:[~2015-01-28 14:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-25 12:06 [Qemu-devel] [PATCH] linux-user/syscall.c: Let all lock_user_struct() and unlock_user_struct() paired with each other Chen Gang S
2015-01-25 12:49 ` Peter Maydell
2015-01-25 21:59 ` Chen Gang S
2015-01-25 22:10 ` Peter Maydell
2015-01-26 14:59 ` Chen Gang S
2015-01-26 15:01 ` Peter Maydell
2015-01-26 23:02 ` Chen Gang S
2015-01-28 14:27 ` Riku Voipio [this message]
2015-01-28 22:09 ` Chen Gang S
2015-01-28 22:36 ` Peter Maydell
2015-01-29 1:37 ` Chen Gang S
2015-02-04 23:03 ` Chen Gang S
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=20150128142705.GA22971@afflict.kos.to \
--to=riku.voipio@iki.fi \
--cc=gang.chen@sunrus.com.cn \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).