From: Sasha Levin <sashal@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Cc: stable@vger.kernel.org, Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: Newer stable-tools
Date: Mon, 12 Apr 2021 19:27:44 -0400 [thread overview]
Message-ID: <YHTXcK3mXRUKTAAf@sashalap> (raw)
In-Reply-To: <5e5195b3-a2e9-471e-cbdd-0951f13ecbb0@canonical.com>
On Mon, Apr 12, 2021 at 06:50:00PM +0200, Krzysztof Kozlowski wrote:
>On 12/04/2021 18:21, Sasha Levin wrote:
>> Hey Krzysztof!
>>
>> On Mon, Apr 12, 2021 at 12:58:16PM +0200, Krzysztof Kozlowski wrote:
>>> Hi Greg, Sasha and everyone,
>>>
>>> I am looking at stable-tools from Sasha [1] in hope in re-using it. The
>>> problem I want to solve is to find easier commits in the distro tree,
>>> which were fixed or reverted upstream. Something like steal-commits from
>>> the stable-tools [1].
>>
>> You're probably looking for stable-has-fixes :)
>>
>>> However the tools themself were not updated since some time and have
>>> several issues, so the questions are:
>>> 1. Do you have somewhere updated version which you would like to share?
>>
>> So I've cleaned up and pushed the few patches I had locally to that
>> repo. It's not that it's abandoned, but rather it was working just fine
>> for me for the past few years so there wasn't anything too big done on
>> that front.
>>
>>> 2. Do you have other stable-toolset which you could share?
>>
>> FWIW, Greg has his own set of scripts: https://github.com/gregkh/gregkh-linux/tree/master/scripts
>
>Thanks, I'll try your changes and take a look at Greg's scripts.
Let me know if something doesn't seem to work out, I'd be happy to help
out here.
--
Thanks,
Sasha
prev parent reply other threads:[~2021-04-12 23:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 10:58 Newer stable-tools Krzysztof Kozlowski
2021-04-12 16:21 ` Sasha Levin
2021-04-12 16:50 ` Krzysztof Kozlowski
2021-04-12 23:27 ` Sasha Levin [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=YHTXcK3mXRUKTAAf@sashalap \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzysztof.kozlowski@canonical.com \
--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