From: Sasha Levin <sashal@kernel.org>
To: Glenn Washburn <development@efficientek.com>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
Jeff Dike <jdike@addtoit.com>,
Richard Weinberger <richard@nod.at>
Subject: Re: Patch "um: port_user: Improve error handling when port-helper is not found" has been added to the 5.17-stable tree
Date: Sun, 22 May 2022 12:34:06 -0400 [thread overview]
Message-ID: <Yopl/v3SQoaaPmUJ@sashalap> (raw)
In-Reply-To: <20220520140515.35ab0497@crass-HP-ZBook-15-G2>
On Fri, May 20, 2022 at 02:05:15PM -0500, Glenn Washburn wrote:
>Resending this because stable@vger.kernel.org using wrong header field.
>Apologize for duplicates.
>
>On Thu, 19 May 2022 09:52:07 -0400
>Sasha Levin <sashal@kernel.org> wrote:
>
>> This is a note to let you know that I've just added the patch titled
>>
>> um: port_user: Improve error handling when port-helper is not found
>>
>> to the 5.17-stable tree which can be found at:
>> http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>>
>> The filename of the patch is:
>> um-port_user-improve-error-handling-when-port-helper.patch
>> and it can be found in the queue-5.17 subdirectory.
>>
>> If you, or anyone else, feels it should not be added to the stable tree,
>> please let <stable@vger.kernel.org> know about it.
>
>First, I should say that I'm not familiar with the process so I'm
>likely to be wrong on any number of things. Second I'm the author of
>this patch and I would like to see this included in the stable trees.
>However, it appears to me that there is a problem in including just this
>patch, as it depends on a previous patch which does not appear to be
>applied[1].
Right, I've dropped it.
>The the afore mentioned patch that this patch depends on "env" is
>declared and set. Without it, I'd expect this to fail to compile. As
>such, I may be wrong in that the dependent patch was not already
>included because I'd expect there to have been a compile test prior to
>this patch getting to this phase.
>
>My suspicion is that the stable trees try to not include new
>functionality, which the missing patch may have been considered to have
>done, and thus was not included. If its deemed undesirable to include
>the missing patch, this "if" block can be removed. Although, I think
>the missing patch is valuable enough to include.
>
>The above goes for all the stable branches that this patch is set to be
>included in.
Could you provide a list of patches that are needed here?
--
Thanks,
Sasha
next prev parent reply other threads:[~2022-05-22 16:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220519135207.392505-1-sashal@kernel.org>
2022-05-20 19:05 ` Patch "um: port_user: Improve error handling when port-helper is not found" has been added to the 5.17-stable tree Glenn Washburn
2022-05-22 16:34 ` Sasha Levin [this message]
2022-05-26 4:16 ` Glenn Washburn
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=Yopl/v3SQoaaPmUJ@sashalap \
--to=sashal@kernel.org \
--cc=development@efficientek.com \
--cc=jdike@addtoit.com \
--cc=richard@nod.at \
--cc=stable-commits@vger.kernel.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