From: Jan Kara <jack@suse.cz>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Jan Kara <jack@suse.cz>,
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 mm tree
Date: Tue, 31 Jan 2023 13:23:14 +0100 [thread overview]
Message-ID: <20230131122314.umasrmx2hwe2epdx@quack3> (raw)
In-Reply-To: <20230131145654.768c6149@canb.auug.org.au>
Hello!
On Tue 31-01-23 14:56:54, Stephen Rothwell wrote:
> The following commit is also in the ext3 tree as a different commit
> (but the same patch):
>
> 05a4851d2729 ("fs: gracefully handle ->get_block not mapping bh in __mpage_writepage")
>
> This is commit
>
> 7010839ccfd4 ("fs: gracefully handle ->get_block not mapping bh in __mpage_writepage")
>
> in the ext3 tree.
Yes, as we already discussed with Andrew, I've merged the patch to my tree
because otherwise UDF fixes result in triggering this problem and crashing
machine left-and-right (which results in a flood of emails from testing
infrastructure). So carrying the patch in my tree seems like by far
the simplest option (otherwise I'd have to either rebase on top of MM tree
or pull MM tree into my tree, neither of which looks particularly
attractive).
Honza
[1] https://lore.kernel.org/all/20230127133213.su4cl6zuiuuv2p35@quack3
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2023-01-31 12:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 3:56 Stephen Rothwell
2023-01-31 12:23 ` Jan Kara [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-18 11:28 Stephen Rothwell
2025-02-16 11:24 Stephen Rothwell
2024-07-31 23:38 Stephen Rothwell
2024-07-18 23:15 Stephen Rothwell
2024-07-14 21:27 Stephen Rothwell
2023-07-23 23:03 Stephen Rothwell
2023-03-15 2:22 Stephen Rothwell
2023-01-31 2:53 Stephen Rothwell
2023-01-24 2:55 Stephen Rothwell
2023-01-16 4:26 Stephen Rothwell
2023-01-05 2:50 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=20230131122314.umasrmx2hwe2epdx@quack3 \
--to=jack@suse.cz \
--cc=akpm@linux-foundation.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
all inboxes | Powered by JetHome®