Linux ACPI
 help / color / mirror / Atom feed
From: James Morse <james.morse@arm.com>
To: 乱石 <zhangliguang@linux.alibaba.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Len Brown <lenb@kernel.org>, Tony Luck <tony.luck@intel.com>,
	Borislav Petkov <bp@alien8.de>,
	linux-acpi@vger.kernel.org
Subject: Re: [PATCH v4] ACPI / APEI: release resources if gen_pool_add fails
Date: Fri, 26 Jul 2019 15:09:59 +0100	[thread overview]
Message-ID: <4d523cd0-cb09-3706-b417-bc118e821908@arm.com> (raw)
In-Reply-To: <794d2bd0-af4f-8935-296f-b4cedd542800@linux.alibaba.com>

Hi Liguang,

On 26/07/2019 10:29, 乱石 wrote:
> 在 2019/7/25 20:46, James Morse 写道:
>> On 15/07/2019 07:58, luanshi wrote:
>>> To avoid memory leaks, destroy ghes_estatus_pool and release memory
>>> allocated via vmalloc() on errors in ghes_estatus_pool_init().
>>>
>>> Signed-off-by: Liguang Zhang <zhangliguang@linux.alibaba.com>
>>> ---
>> Playing spot-the-difference with [v3], you've moved an empty line.
>>
>> Please include a change log in this space below the '---' tearoff. This helps reviewers
>> know what you changed between versions, and git knows not to add stuff in here to the log.
>>
>> This is still:
>> Reviewed-by: James Morse <james.morse@arm.com>
> 
> Thanks for your review. Because your reviewed-by was given ealier, and the code is
> reconstructed,
> 
> so I remove the reviewed-by. I will send v5 by your suggestions.

There is no need to post a new version just to pick up the tags.

Having a versioned changelog on your future work makes it easier for reviewers to know
what changed between versions.


Thanks,

James

  reply	other threads:[~2019-07-26 14:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-15  6:58 [PATCH v4] ACPI / APEI: release resources if gen_pool_add fails luanshi
2019-07-25 12:46 ` James Morse
2019-07-26  9:29   ` 乱石
2019-07-26 14:09     ` James Morse [this message]
2019-08-13 17:16 ` [PATCH v4.1] " Borislav Petkov
2019-08-26  9:06   ` Rafael J. Wysocki

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=4d523cd0-cb09-3706-b417-bc118e821908@arm.com \
    --to=james.morse@arm.com \
    --cc=bp@alien8.de \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=tony.luck@intel.com \
    --cc=zhangliguang@linux.alibaba.com \
    /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