From: Frank Scheiner <frank.scheiner@web.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: akpm@linux-foundation.org, allen.lkml@gmail.com,
broonie@kernel.org, conor@kernel.org, f.fainelli@gmail.com,
jonathanh@nvidia.com, linux-kernel@vger.kernel.org,
linux@roeck-us.net, lkft-triage@lists.linaro.org,
patches@kernelci.org, patches@lists.linux.dev, pavel@denx.de,
rwarsow@gmx.de, shuah@kernel.org, srw@sladewatkins.net,
stable@vger.kernel.org, sudipm.mukherjee@gmail.com,
torvalds@linux-foundation.org, "Tomáš Glozar" <tglozar@gmail.com>
Subject: Re: [PATCH 4.19 00/66] 4.19.318-rc1 review
Date: Wed, 17 Jul 2024 11:34:32 +0200 [thread overview]
Message-ID: <8bc5fd5c-e3ae-436a-94f9-8806841e34ad@web.de> (raw)
In-Reply-To: <2024071700-precision-basin-0e6e@gregkh>
On 17.07.24 11:30, Greg KH wrote:
> On Wed, Jul 17, 2024 at 10:54:40AM +0200, Frank Scheiner wrote:
>> fb3739759474d150a9927b920a80ea2afb4c2a51 (from mainline) should be
>> included in linux-4.19.y, if a589979f345720aca32ff43a2ccaa16a70871b9e
>> stays in.
>
> I do not know what commit a589979f345720aca32ff43a2ccaa16a70871b9e is,
> sorry. If you rea referring to commits in the -rc tree, please don't as
> that tree is rebased and regenerated all the time. In fact, my scripts
> don't even save a local copy when they are generated so I have no idea
> how to find this :(
I see. Makes sense.
> Please refer to the commit id in Linus's tree so I have a hint as to
> what is happening here.
Ok, will do in the future.
>> ****
>>
>> ## Long version ##
>>
>> It looks like:
>>
>> ```
>> hpet: Support 32-bit userspace
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/?h=linux-4.19.y&id=a589979f345720aca32ff43a2ccaa16a70871b9e
>> ```
>
> Ah, you mean commit 4e60131d0d36 ("hpet: Support 32-bit userspace"),
> right?
Exactly.
> [...]
>> So fb3739759474d150a9927b920a80ea2afb4c2a51 should be included in
>> linux-4.19.y, too, if a589979f345720aca32ff43a2ccaa16a70871b9e stays in.
>
> Ok, I'll queue this one up as well, hopefully nothing else breaks...
+1
Cheers,
Frank
next prev parent reply other threads:[~2024-07-17 9:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 15:30 Greg Kroah-Hartman
2024-07-16 20:11 ` Pavel Machek
2024-07-16 21:00 ` Naresh Kamboju
2024-07-17 6:21 ` Greg Kroah-Hartman
2024-07-17 8:54 ` Frank Scheiner
2024-07-17 9:30 ` Greg KH
2024-07-17 9:34 ` Frank Scheiner [this message]
2024-07-17 15:57 ` Shuah Khan
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=8bc5fd5c-e3ae-436a-94f9-8806841e34ad@web.de \
--to=frank.scheiner@web.de \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=tglozar@gmail.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®