All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Gang S <gang.chen@sunrus.com.cn>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
	Riku Voipio <riku.voipio@iki.fi>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-trivial] [PATCH] linux-user/syscall.c: Let all lock_user_struct() and unlock_user_struct() paired with each other
Date: Mon, 26 Jan 2015 22:59:55 +0800	[thread overview]
Message-ID: <54C6566B.6050205@sunrus.com.cn> (raw)
In-Reply-To: <CAFEAcA9mqzpHsWcyDdzBYDWdxsR1AoDy3akgHCaMUbjZ0zh=0Q@mail.gmail.com>

On 1/26/15 06:10, Peter Maydell wrote:
> On 25 January 2015 at 21:59, Chen Gang S <gang.chen@sunrus.com.cn> wrote:
>> On 1/25/15 20:49, Peter Maydell wrote:
>>> Are you claiming that you've reviewed *all* the code in this
>>> file for mismatched lock/unlock calls? If so, it would be nice
>>> to say so explicitly in the commit message. If not, it would be
>>> nice if the commit message was clearer about what areas of the
>>> code it applied to. The code changes are correct, though.
>>>
>>
>> At present, I finished all lock_user_struct() and unlock_user_struct()
>> in "linux-user/syscall.c". For me, after this patch, they are all OK.
>>
>> But for all lock/unlock in "linux-user/syscall.c", for me, I am doubting
>> several areas, but I did not send patch for them:
>>
>>  - I need check them carefully again to be sure they are really issue:
>>
>>    Read the related code again and again, if I really treat it as an
>>    issue, I shall make related patch (and pass compiling, at least).
>>
>>  - I have no enough time resources on it:
> 
> That's fine. I'm definitely not asking you to do this work.

OK, thanks. :-)

> 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.

Welcome to help improve the patch comments. If necessary to send patch
v2, please let me know, I shall try.


Thanks.
-- 
Chen Gang

Open, share, and attitude like air, water, and life which God blessed


WARNING: multiple messages have this Message-ID (diff)
From: Chen Gang S <gang.chen@sunrus.com.cn>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
	Riku Voipio <riku.voipio@iki.fi>,
	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: Mon, 26 Jan 2015 22:59:55 +0800	[thread overview]
Message-ID: <54C6566B.6050205@sunrus.com.cn> (raw)
In-Reply-To: <CAFEAcA9mqzpHsWcyDdzBYDWdxsR1AoDy3akgHCaMUbjZ0zh=0Q@mail.gmail.com>

On 1/26/15 06:10, Peter Maydell wrote:
> On 25 January 2015 at 21:59, Chen Gang S <gang.chen@sunrus.com.cn> wrote:
>> On 1/25/15 20:49, Peter Maydell wrote:
>>> Are you claiming that you've reviewed *all* the code in this
>>> file for mismatched lock/unlock calls? If so, it would be nice
>>> to say so explicitly in the commit message. If not, it would be
>>> nice if the commit message was clearer about what areas of the
>>> code it applied to. The code changes are correct, though.
>>>
>>
>> At present, I finished all lock_user_struct() and unlock_user_struct()
>> in "linux-user/syscall.c". For me, after this patch, they are all OK.
>>
>> But for all lock/unlock in "linux-user/syscall.c", for me, I am doubting
>> several areas, but I did not send patch for them:
>>
>>  - I need check them carefully again to be sure they are really issue:
>>
>>    Read the related code again and again, if I really treat it as an
>>    issue, I shall make related patch (and pass compiling, at least).
>>
>>  - I have no enough time resources on it:
> 
> That's fine. I'm definitely not asking you to do this work.

OK, thanks. :-)

> 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.

Welcome to help improve the patch comments. If necessary to send patch
v2, please let me know, I shall try.


Thanks.
-- 
Chen Gang

Open, share, and attitude like air, water, and life which God blessed

  reply	other threads:[~2015-01-26 14:52 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-25 12:06 [Qemu-trivial] [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:06 ` [Qemu-devel] " Chen Gang S
2015-01-25 12:49 ` [Qemu-trivial] " Peter Maydell
2015-01-25 12:49   ` [Qemu-devel] " Peter Maydell
2015-01-25 21:59   ` [Qemu-trivial] " Chen Gang S
2015-01-25 21:59     ` [Qemu-devel] " Chen Gang S
2015-01-25 22:10     ` [Qemu-trivial] " Peter Maydell
2015-01-25 22:10       ` [Qemu-devel] " Peter Maydell
2015-01-26 14:59       ` Chen Gang S [this message]
2015-01-26 14:59         ` Chen Gang S
2015-01-26 15:01         ` [Qemu-trivial] " Peter Maydell
2015-01-26 15:01           ` [Qemu-devel] " Peter Maydell
2015-01-26 23:02           ` [Qemu-trivial] " Chen Gang S
2015-01-26 23:02             ` [Qemu-devel] " Chen Gang S
2015-01-28 14:27           ` [Qemu-trivial] " Riku Voipio
2015-01-28 14:27             ` [Qemu-devel] " Riku Voipio
2015-01-28 22:09             ` [Qemu-trivial] " Chen Gang S
2015-01-28 22:09               ` [Qemu-devel] " Chen Gang S
2015-01-28 22:36               ` [Qemu-trivial] " Peter Maydell
2015-01-28 22:36                 ` Peter Maydell
2015-01-29  1:37                 ` [Qemu-trivial] " Chen Gang S
2015-01-29  1:37                   ` Chen Gang S
2015-02-04 23:03                   ` [Qemu-trivial] " 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=54C6566B.6050205@sunrus.com.cn \
    --to=gang.chen@sunrus.com.cn \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.