From: "Darrick J. Wong" <djwong@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Christian Brauner <brauner@kernel.org>,
Christoph Hellwig <hch@lst.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the vfs-brauner tree
Date: Mon, 18 Sep 2023 13:52:06 -0700 [thread overview]
Message-ID: <20230918205206.GA348037@frogsfrogsfrogs> (raw)
In-Reply-To: <20230915093953.310503ee@canb.auug.org.au>
On Fri, Sep 15, 2023 at 09:39:53AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> The following commit is also in the iomap tree as a different commit
> (but the same patch):
>
> de5b0b257ee3 ("iomap: handle error conditions more gracefully in iomap_to_bh")
>
> This is commit
>
> 4aa8cdd5e523 ("iomap: handle error conditions more gracefully in iomap_to_bh")
>
> in the iomap tree.
Christian, do you want to push this to Linus instead of me? I've a
couple more fixes that I'm about to send out to fsdevel and could just
roll all the iomap stuff into a single branch... but if you were about
to this to Linus I don't mind letting that happen.
--D
> --
> Cheers,
> Stephen Rothwell
next prev parent reply other threads:[~2023-09-18 20:52 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 23:39 linux-next: duplicate patch in the vfs-brauner tree Stephen Rothwell
2023-09-18 20:52 ` Darrick J. Wong [this message]
2023-09-19 12:34 ` Christian Brauner
2023-09-19 15:43 ` Darrick J. Wong
2023-09-20 12:09 ` Christian Brauner
-- strict thread matches above, loose matches on Subject: below --
2025-12-18 5:32 Stephen Rothwell
2025-08-21 1:02 Stephen Rothwell
2025-08-21 5:24 ` Greg KH
2025-07-07 23:51 Stephen Rothwell
2025-07-08 8:35 ` Christian Brauner
2025-07-08 21:51 ` Stephen Rothwell
2025-05-20 23:45 Stephen Rothwell
2025-05-20 23:48 ` Stephen Rothwell
2025-04-16 22:49 Stephen Rothwell
2025-04-22 8:03 ` Christian Brauner
2025-01-16 1:16 Stephen Rothwell
2025-01-19 21:06 ` Stephen Rothwell
2025-01-09 0:18 Stephen Rothwell
2025-01-20 21:39 ` Stephen Rothwell
2024-08-25 22:24 Stephen Rothwell
2024-08-26 12:13 ` Christian Brauner
2024-08-15 22:55 Stephen Rothwell
2024-07-01 3:21 Stephen Rothwell
2024-06-13 0:48 Stephen Rothwell
2024-06-13 0:51 ` Stephen Rothwell
2024-06-13 2:21 ` Andrew Morton
2024-06-13 12:17 ` Christian Brauner
2024-06-13 19:43 ` Andrew Morton
2024-06-13 20:06 ` Marion & Christophe JAILLET
2024-03-18 21:23 Stephen Rothwell
2024-03-06 22:02 Stephen Rothwell
2024-02-05 5:23 Stephen Rothwell
2023-08-06 22:37 Stephen Rothwell
2023-07-17 0:11 Stephen Rothwell
2023-07-19 6:16 ` Christian Brauner
2023-07-19 23:28 ` Tyler Hicks
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=20230918205206.GA348037@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=brauner@kernel.org \
--cc=hch@lst.de \
--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