mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [git pull] the rest of write_one_page() series
Date: Tue, 25 Apr 2023 03:35:11 +0100	[thread overview]
Message-ID: <20230425023511.GO3390869@ZenIV> (raw)
In-Reply-To: <CAHk-=wibAWqh3JqWaWfi=JWNAz3v_qb7LZ+76qF+PKEJciHbGA@mail.gmail.com>

On Mon, Apr 24, 2023 at 07:24:05PM -0700, Linus Torvalds wrote:
> On Sun, Apr 23, 2023 at 9:26 PM Al Viro <viro@zeniv.linux.org.uk> wrote:
> >
> > write_one_page series
> 
> Hmm. These pull requests really could have done with better descriptions.
> 
> Yes, I see what it's doing, but I'd really like to have better merge
> messages from the pull request.

Point...  With this one it would be along the lines of "the parts of
Christoph's write_one_page() elimination series that missed the previous
merge window".

pull-fd: "routine whack-a-mole for new unwarranted callers of fget() that
really ought to have been using fdget() - that kind of stuff keeps
cropping up and needs to be hunted down once in a while".

pull-old_dio: "For a while fs/direct-io.c had been trying to keep up with
filesystems' demands; eventually the tricky cases started to convert to
iomap-based variant, so some of the stuff added for e.g. btrfs sake had
become unused.  Longer term we want to get rid of fs/direct-io.c completely,
but for now let's at least undo some of the now-useless complexity there"

pull-nios2, pull-misc: really can't improve the descriptions in those...

  reply	other threads:[~2023-04-25  2:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-24  4:26 Al Viro
2023-04-25  2:24 ` Linus Torvalds
2023-04-25  2:35   ` Al Viro [this message]
2023-04-25  2:42     ` Linus Torvalds
2023-04-25  2:49 ` 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=20230425023511.GO3390869@ZenIV \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®