From: Jonathan Corbet <corbet@lwn.net>
To: Pascal Ernster <git@hardfalcon.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org, allen.lkml@gmail.com, broonie@kernel.org
Subject: Re: [PATCH 6.6 000/186] 6.6.30-rc1 review
Date: Thu, 02 May 2024 08:14:01 -0600 [thread overview]
Message-ID: <87sez08fo6.fsf@meer.lwn.net> (raw)
In-Reply-To: <daf3d612-283b-467a-82b7-bbf04fd8f723@hardfalcon.net>
Pascal Ernster <git@hardfalcon.net> writes:
> [2024-05-02 08:50] Greg Kroah-Hartman:
>> On Thu, May 02, 2024 at 08:44:30AM +0200, Pascal Ernster wrote:
>>> [2024-04-30 12:37] Greg Kroah-Hartman:
>>>> This is the start of the stable review cycle for the 6.6.30 release.
>>>> There are 186 patches in this series, all will be posted as a response
>>>> to this one. If anyone has any issues with these being applied, please
>>>> let me know.
>>>>
>>>> Responses should be made by Thu, 02 May 2024 10:30:27 +0000.
>>>> Anything received after that time might be too late.
>>>
>>> Hi, 6.6.30-rc1 is running fine on an x86_64 Haswell VM.
>>>
>>> Note that I have *not* tested building the kernel documentation, and I
>>> suspect that building the documentation with docutils >= 0.21 would likely
>>> fail without the patch from
>>>
>>> https://lore.kernel.org/all/faf5fa45-2a9d-4573-9d2e-3930bdc1ed65@gmail.com/
>>
>> What is the git id of this in Linus's tree?
>
>
> Hi,
>
>
> AFAICT this has not been merged into either Linus' tree nor into
> linux-next nor into docs-next.
>
> I've added Jonathan Corbet because he seems to be the most likely
> maintainer for Documentation/sphinx/kernel_include.py if I
> understand/interpret the MAINTAINERS file correctly.
The patch was sent yesterday, so I've not had time to apply it yet.
That may happen today.
Thanks,
jon
prev parent reply other threads:[~2024-05-02 14:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 10:37 Greg Kroah-Hartman
2024-04-30 16:19 ` Harshit Mogalapalli
2024-04-30 16:48 ` SeongJae Park
2024-04-30 19:17 ` Florian Fainelli
2024-05-01 8:39 ` Ron Economos
2024-05-01 9:03 ` Naresh Kamboju
2024-05-01 11:34 ` Miguel Ojeda
2024-05-01 12:25 ` Takeshi Ogasawara
2024-05-01 13:38 ` Jon Hunter
2024-05-01 13:41 ` Mark Brown
2024-05-01 19:47 ` Pavel Machek
2024-05-02 3:01 ` Shuah Khan
2024-05-02 6:44 ` Pascal Ernster
2024-05-02 6:50 ` Greg Kroah-Hartman
2024-05-02 7:29 ` Pascal Ernster
2024-05-02 14:14 ` Jonathan Corbet [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=87sez08fo6.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=git@hardfalcon.net \
--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=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®