From: NeilBrown <neilb@suse.com>
To: Shaohua Li <shli@fb.com>, Christoph Hellwig <hch@lst.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: two small raid5 cache updates
Date: Wed, 09 Dec 2015 09:57:07 +1100 [thread overview]
Message-ID: <87egewr1ks.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <20151203044750.GA3111265@devbig084.prn1.facebook.com>
[-- Attachment #1: Type: text/plain, Size: 304 bytes --]
On Thu, Dec 03 2015, Shaohua Li wrote:
> On Wed, Dec 02, 2015 at 05:06:37PM +0100, Christoph Hellwig wrote:
>> The first is a trival cleanup, the second a similarly trivial reduction
>> in memory usage.
>
> Looks good, thanks!
>
> Reviewed-by: Shaohua Li <shli@fb.com>
Both applied, thanks.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
prev parent reply other threads:[~2015-12-08 22:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 16:06 two small raid5 cache updates Christoph Hellwig
2015-12-02 16:06 ` [PATCH 1/2] raid5-cache: simplify r5l_move_io_unit_list Christoph Hellwig
2015-12-02 16:06 ` [PATCH 2/2] raid5-cache: free meta_page earlier Christoph Hellwig
2015-12-03 4:47 ` two small raid5 cache updates Shaohua Li
2015-12-08 22:57 ` NeilBrown [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=87egewr1ks.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=hch@lst.de \
--cc=linux-raid@vger.kernel.org \
--cc=shli@fb.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;
as well as URLs for NNTP newsgroup(s).