From: Jens Axboe <axboe@kernel.dk>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Christian Brauner <brauner@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patches in the block tree
Date: Wed, 20 Dec 2023 20:11:34 -0700 [thread overview]
Message-ID: <f31dae39-7c62-453a-8ca5-bd0b0e58769f@kernel.dk> (raw)
In-Reply-To: <20231221135602.12bf82f5@canb.auug.org.au>
On 12/20/23 7:56 PM, Stephen Rothwell wrote:
> Hi all,
>
> The following commits are also in the vfs-brauner tree as different
> commits (but the same patches):
>
> 24fa3ae9467f ("file: remove pointless wrapper")
> 253ca8678d30 ("Improve __fget_files_rcu() code generation (and thus __fget_light())")
> 372a34e66fb7 ("fs: replace f_rcuhead with f_task_work")
> 4e94ddfe2aab ("file: remove __receive_fd()")
> 7cb537b6f6d7 ("file: massage cleanup of files that failed to open")
> a88c955fcfb4 ("file: s/close_fd_get_file()/file_close_fd()/g")
> eac9189c9619 ("file: stop exposing receive_fd_user()")
Hmm confused, assumed vfs.file got rebased again, but doesn't look to be
the case. Christian?
--
Jens Axboe
next prev parent reply other threads:[~2023-12-21 3:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 2:56 linux-next: duplicate patches in the block tree Stephen Rothwell
2023-12-21 3:11 ` Jens Axboe [this message]
2023-12-21 12:29 ` Christian Brauner
2023-12-21 15:32 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2023-12-12 2:02 Stephen Rothwell
2023-12-12 13:38 ` Christian Brauner
2023-12-12 15:01 ` Jens Axboe
2023-08-07 4:51 Stephen Rothwell
2023-08-07 18:16 ` Jens Axboe
2023-02-20 1:02 Stephen Rothwell
2023-02-20 1:47 ` David Howells
2023-02-20 2:49 ` Stephen Rothwell
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=f31dae39-7c62-453a-8ca5-bd0b0e58769f@kernel.dk \
--to=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).