From: SeongJae Park <sj@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: SeongJae Park <sj@kernel.org>,
stable@vger.kernel.org, sashal@kernel.org,
David Gow <davidgow@google.com>,
Daniel Latypov <dlatypov@google.com>,
brendanhiggins@google.com, rmoar@google.com,
linux-kernel@vger.kernel.org, kunit-dev@googlegroups.com,
linux-kselftest@vger.kernel.org, skhan@linuxfoundation.org,
johannes@sipsolutions.net
Subject: Re: [PATCH] kunit: tool: undo type subscripts for subprocess.Popen
Date: Mon, 3 Jul 2023 19:54:11 +0000 [thread overview]
Message-ID: <20230703195411.16567-1-sj@kernel.org> (raw)
In-Reply-To: <2023070322-retype-lanky-6f2d@gregkh>
On Mon, 3 Jul 2023 21:44:53 +0200 Greg KH <gregkh@linuxfoundation.org> wrote:
> On Mon, Jul 03, 2023 at 07:27:04PM +0000, SeongJae Park wrote:
[...]
> > This patch is now in the mainline (e30f65c4b3d671115bf2a9d9ef142285387f2aff).
> > However, this fix is not in 6.4.y yet, so the original issue is reproducible on
> > 6.4.y. Could you please add this to 6.4.y? I confirmed the mainline commit
> > can cleanly applied on latest 6.1.y tree, and it fixes the issue.
>
> As this was not specifically tagged with a "cc: stable..." marking, that
> is why it was not picked up automatically.
I understand that. I thought this would be merged into the mainline before
v6.4 release, but I was wrong.
> Also, we do not normally add patches to any stable releases until it is in a
> released kernel from Linus (i.e. a -rc release), unless you have a specific
> reason for it to be merged earlier.
>
> Should this be merged "now" into the stable trees and not wait for
> 6.5-rc1?
The problem is not urgent, so I can wait until 6.5-rc1.
Thanks,
SJ
>
> thanks,
>
> greg k-h
prev parent reply other threads:[~2023-07-03 19:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-01 18:16 [PATCH] kunit: tool: undo type subscripts for subprocess.Popen Daniel Latypov
2023-05-01 19:10 ` SeongJae Park
2023-05-02 0:04 ` David Gow
2023-06-09 19:09 ` SeongJae Park
2023-06-10 4:15 ` David Gow
2023-06-10 17:56 ` SeongJae Park
2023-07-03 19:27 ` SeongJae Park
2023-07-03 19:44 ` Greg KH
2023-07-03 19:54 ` SeongJae Park [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=20230703195411.16567-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=brendanhiggins@google.com \
--cc=davidgow@google.com \
--cc=dlatypov@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=johannes@sipsolutions.net \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=rmoar@google.com \
--cc=sashal@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).