From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jens Axboe <axboe@kernel.dk>, "Darrick J. Wong" <djwong@kernel.org>
Cc: 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, 7 Aug 2023 14:51:20 +1000 [thread overview]
Message-ID: <20230807145120.6c2080a0@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1254 bytes --]
Hi all,
The following commits are also in the iomap tree as different commits
(but the same patches):
634aae6c3333 ("iomap: support IOCB_DIO_CALLER_COMP")
4d184b3fd1ab ("io_uring/rw: add write support for IOCB_DIO_CALLER_COMP")
d6cb42b086fe ("fs: add IOCB flags related to passing back dio completions")
7e8dcad9affa ("iomap: add IOMAP_DIO_INLINE_COMP")
448373a0bd1d ("iomap: only set iocb->private for polled bio")
661687f531ef ("iomap: treat a write through cache the same as FUA")
0e40c9e86011 ("iomap: use an unsigned type for IOMAP_DIO_* defines")
062ef9f4932e ("iomap: cleanup up iomap_dio_bio_end_io()")
These are commits
8c052fb3002e ("iomap: support IOCB_DIO_CALLER_COMP")
099ada2c8726 ("io_uring/rw: add write support for IOCB_DIO_CALLER_COMP")
9cf3516c29e6 ("fs: add IOCB flags related to passing back dio completions")
7b3c14d1a96b ("iomap: add IOMAP_DIO_INLINE_COMP")
daa99c5a3319 ("iomap: only set iocb->private for polled bio")
3a0be38cc84d ("iomap: treat a write through cache the same as FUA")
44842f647346 ("iomap: use an unsigned type for IOMAP_DIO_* defines")
3486237c6fe8 ("iomap: cleanup up iomap_dio_bio_end_io()")
in the iomap tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-08-07 4:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 4:51 Stephen Rothwell [this message]
2023-08-07 18:16 ` linux-next: duplicate patches in the block tree Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2024-07-22 22:11 Stephen Rothwell
2024-07-22 22:14 ` 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
2023-12-12 2:02 Stephen Rothwell
2023-12-12 13:38 ` Christian Brauner
2023-12-12 15:01 ` 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=20230807145120.6c2080a0@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=axboe@kernel.dk \
--cc=djwong@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.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