public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jens Axboe <axboe@kernel.dk>, Steve French <smfrench@gmail.com>
Cc: CIFS <linux-cifs@vger.kernel.org>,
	David Howells <dhowells@redhat.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: duplicate patches in the block tree
Date: Mon, 20 Feb 2023 12:02:34 +1100	[thread overview]
Message-ID: <20230220120234.161a6002@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]

Hi all,

The following commits are also in Linus Torvalds' tree as different
commits (but the same patches):

  78e11ab5adf7 ("mm: Pass info, not iter, into filemap_get_pages()")
  a53cad008099 ("splice: Add a func to do a splice from a buffered file without ITER_PIPE")
  f2aa2c5707ac ("splice: Add a func to do a splice from an O_DIRECT file without ITER_PIPE")
  51e851b5d16f ("iov_iter: Define flags to qualify page extraction.")
  0fff5a38a770 ("iov_iter: Add a function to extract a page list from an iterator")

These are commits

  c935d7b85ae1 ("mm: Pass info, not iter, into filemap_get_pages()")
  03aaa67b45e7 ("splice: Add a func to do a splice from a buffered file without ITER_PIPE")
  1dba0a6d58da ("splice: Add a func to do a splice from an O_DIRECT file without ITER_PIPE")
  f48b6bcd02a1 ("iov_iter: Define flags to qualify page extraction.")
  c82edb69b878 ("iov_iter: Add a function to extract a page list from an iterator")

in the cifs tree.

(A few of these are not exactly the same, but very similar)

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2023-02-20  1:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-20  1:02 Stephen Rothwell [this message]
2023-02-20  1:47 ` linux-next: duplicate patches in the block tree David Howells
2023-02-20  2:49   ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2023-08-07  4:51 Stephen Rothwell
2023-08-07 18:16 ` Jens Axboe
2023-12-12  2:02 Stephen Rothwell
2023-12-12 13:38 ` Christian Brauner
2023-12-12 15:01   ` Jens Axboe
2023-12-21  2:56 Stephen Rothwell
2023-12-21  3:11 ` Jens Axboe
2023-12-21 12:29   ` Christian Brauner
2023-12-21 15:32     ` Jens Axboe
2024-07-22 22:11 Stephen Rothwell
2024-07-22 22:14 ` Jens Axboe

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=20230220120234.161a6002@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=axboe@kernel.dk \
    --cc=dhowells@redhat.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=smfrench@gmail.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