From: Christoph Hellwig <hch@infradead.org>
To: Vratislav Bendel <vbendel@redhat.com>
Cc: linux-xfs@vger.kernel.org,
"Darrick J . Wong" <darrick.wong@oracle.com>,
Brian Foster <bfoster@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xfs: Correctly invert xfs_buftarg LRU isolation logic
Date: Thu, 8 Mar 2018 00:08:37 -0800 [thread overview]
Message-ID: <20180308080837.GB15163@infradead.org> (raw)
In-Reply-To: <20180306102638.25322-1-vbendel@redhat.com>
Looks good,
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2018-03-08 8:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 10:26 [PATCH] xfs: Correctly invert xfs_buftarg LRU isolation logic Vratislav Bendel
2018-03-07 0:34 ` Darrick J. Wong
2018-03-08 8:08 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-28 15:49 Vratislav Bendel
2018-02-28 19:08 ` Luis R. Rodriguez
2018-03-01 17:39 ` Brian Foster
2018-03-01 22:48 ` Darrick J. Wong
2018-03-02 16:36 ` Darrick J. Wong
2018-03-05 10:19 ` Vratislav Bendel
2018-03-05 18:52 ` Darrick J. Wong
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=20180308080837.GB15163@infradead.org \
--to=hch@infradead.org \
--cc=bfoster@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=vbendel@redhat.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).