From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ryusuke Konishi <konishi.ryusuke@gmail.com>
Cc: Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org,
syzbot+d6ca2daf692c7a82f959@syzkaller.appspotmail.com,
Andrew Morton <akpm@linux-foundation.org>,
linux-nilfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: FAILED: Patch "nilfs2: fix kernel bug due to missing clearing of checked flag" failed to apply to v6.6-stable tree
Date: Wed, 6 Nov 2024 07:34:17 +0100 [thread overview]
Message-ID: <2024110608-shut-strenuous-04c8@gregkh> (raw)
In-Reply-To: <CAKFNMomd0cxe-hP0CoNH7ERvrPCDhz22sRs=8086-j3H=OqOxg@mail.gmail.com>
On Wed, Nov 06, 2024 at 03:21:39PM +0900, Ryusuke Konishi wrote:
> Hi Sasha
>
> About 6 hours ago, I posted an adjusted patch to the list (and to
> Greg) that allows for backporting of this patch to 6.6-stable and
> earlier.
>
> The patch is titled "[PATCH 4.19 5.4 5.10 5.15 6.1 6.6] nilfs2: fix
> kernel bug due to missing clearing of checked flag".
>
> (or https://lkml.kernel.org/r/20241105235654.15044-1-konishi.ryusuke@gmail.com )
>
> Normally, Greg would pick up the adjusted patch and apply it, and it
> would be backported without any problems, but if the backport of the
> adjusted patch I requested has been rejected, I would like to ask for
> your confirmation.
>
> If it is a misunderstanding, I will wait for Greg's work, but is the
> process different from usual?
I got it now, thanks!
greg k-h
prev parent reply other threads:[~2024-11-06 6:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 2:09 FAILED: Patch "nilfs2: fix kernel bug due to missing clearing of checked flag" failed to apply to v6.6-stable tree Sasha Levin
2024-11-06 6:21 ` Ryusuke Konishi
2024-11-06 6:34 ` Greg Kroah-Hartman [this message]
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=2024110608-shut-strenuous-04c8@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=konishi.ryusuke@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=syzbot+d6ca2daf692c7a82f959@syzkaller.appspotmail.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;
as well as URLs for NNTP newsgroup(s).