From: David Sterba <dsterba@suse.cz>
To: Matthew Wilcox <willy@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [GIT PULL] Folio fixes for 5.18
Date: Tue, 5 Apr 2022 14:08:48 +0200 [thread overview]
Message-ID: <20220405120848.GV15609@twin.jikos.cz> (raw)
In-Reply-To: <YkdKgzil38iyc7rX@casper.infradead.org>
On Fri, Apr 01, 2022 at 07:54:59PM +0100, Matthew Wilcox wrote:
> A mixture of odd changes that didn't quite make it into the original
> pull and fixes for things that did. Also the readpages changes had to
> wait for the NFS tree to be pulled first.
>
> The following changes since commit d888c83fcec75194a8a48ccd283953bdba7b2550:
>
> fs: fix fd table size alignment properly (2022-03-29 23:29:18 -0700)
>
> are available in the Git repository at:
>
> git://git.infradead.org/users/willy/pagecache.git tags/folio-5.18d
>
> for you to fetch changes up to 5a60542c61f3cce6e5dff2a38c8fb08a852a517b:
>
> btrfs: Remove a use of PAGE_SIZE in btrfs_invalidate_folio() (2022-04-01 14:40:44 -0400)
Matthew, can you please always CC linux-btrfs@vger.kernel.org for any
patches that touch code under fs/btrfs? I've only noticed your folio
updates in this pull request. Some of the changes are plain API switch,
that's fine but I want to know about that, some changes seem to slightly
modify logic that I'd really like to review and there are several missed
opportunities to fix coding style. Thanks.
next prev parent reply other threads:[~2022-04-05 12:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 18:54 Matthew Wilcox
2022-04-01 21:45 ` pr-tracker-bot
2022-04-05 12:08 ` David Sterba [this message]
2022-04-05 14:22 ` Matthew Wilcox
2022-04-05 18:09 ` David Sterba
2022-04-06 5:55 ` Christoph Hellwig
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=20220405120848.GV15609@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=torvalds@linux-foundation.org \
--cc=willy@infradead.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