linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Matthew Wilcox <willy@infradead.org>, Ted Ts'o <tytso@mit.edu>,
	Gao Xiang <xiang@kernel.org>, Linux-MM <linux-mm@kvack.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Page cache changes for 5.19
Date: Wed, 25 May 2022 11:19:25 +0800	[thread overview]
Message-ID: <Yo2gPUN/6u0cZ80A@B-P7TQMD6M-0146.local> (raw)
In-Reply-To: <CAHk-=wj2kKMnxUu65zbJ28t0azRv3-EHpKaaecYTcLiNtw_eMQ@mail.gmail.com>

Hi Linus,

On Tue, May 24, 2022 at 08:06:32PM -0700, Linus Torvalds wrote:
> On Tue, May 24, 2022 at 12:34 PM Matthew Wilcox <willy@infradead.org> wrote:
> >
> > These are the page cache changes for 5.19.  There are a few conflicts
> > with other peoples work:
> 
> Hmm. Also the ext4 symlink change (which made your changes there go
> away) and the erofs fscache code.

Thanks for noticing! At a quick look, I think erofs/fscache.c part is fine,
but will test on our side again!

(Actually, Matthew's PR mentioned a version formed by Stephen...
 erofs:
https://lore.kernel.org/linux-next/20220502180425.7305c335@canb.auug.org.au/

 but your version also looks good to me, thanks! )

Thanks,
Gao Xiang

> 
> I think I sorted it all out correctly and it looked very
> straightforward, but it would probably be a good idea for people to
> double-check despite that.
> 
>                 Linus


  reply	other threads:[~2022-05-25  3:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-24 19:34 Matthew Wilcox
2022-05-25  3:06 ` Linus Torvalds
2022-05-25  3:19   ` Gao Xiang [this message]
2022-05-25  3:08 ` pr-tracker-bot

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=Yo2gPUN/6u0cZ80A@B-P7TQMD6M-0146.local \
    --to=hsiangkao@linux.alibaba.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    --cc=willy@infradead.org \
    --cc=xiang@kernel.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