From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: 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,
stable@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH 4.9 00/30] 4.9.254-rc1 review
Date: Sat, 30 Jan 2021 12:52:52 +0100 [thread overview]
Message-ID: <YBVIlENhvmBEndsU@kroah.com> (raw)
In-Reply-To: <f39129e5-6d38-6c33-f31e-cf15e4c0399d@nvidia.com>
On Sat, Jan 30, 2021 at 11:12:43AM +0000, Jon Hunter wrote:
>
> On 29/01/2021 19:08, Jon Hunter wrote:
> > On Fri, 29 Jan 2021 12:06:36 +0100, Greg Kroah-Hartman wrote:
> >> This is the start of the stable review cycle for the 4.9.254 release.
> >> There are 30 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 Sun, 31 Jan 2021 10:59:01 +0000.
> >> Anything received after that time might be too late.
> >>
> >> The whole patch series can be found in one patch at:
> >> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.9.254-rc1.gz
> >> or in the git tree and branch at:
> >> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.9.y
> >> and the diffstat can be found below.
> >>
> >> thanks,
> >>
> >> greg k-h
> >
> > All tests passing for Tegra ...
> >
> > Test results for stable-v4.9:
> > 8 builds: 8 pass, 0 fail
> > 16 boots: 16 pass, 0 fail
> > 30 tests: 30 pass, 0 fail
> >
> > Linux version: 4.9.254-rc1-g1aa322729224
> > Boards tested: tegra124-jetson-tk1, tegra20-ventana,
> > tegra210-p2371-2180, tegra30-cardhu-a04
> >
> > Tested-by: Jon Hunter <jonathanh@nvidia.com>
> >
> > Jon
>
>
> For some reason I don't appear to be receiving the 'review' request
> emails. We have a script that checks for them on lore.kernel.org/lkml
> but I don't seem to find them there either ...
>
> https://lore.kernel.org/lkml/?q=%5BPATCH+4.14+00%2F50%5D+4.14.218-rc1+review
>
> https://lore.kernel.org/lkml/?q=%5BPATCH+4.19+00%2F26%5D+4.19.172-rc1+review
>
> I thought it was our mail server but then I would have thought I would
> see them on lore. I often see a delay but they usually arrive within a day.
vger.kernel.org has been having some problems for the past few days in
sending messages out, which is why they wouldn't show up in lore as well
if they never get sent from the server.
I can add you as a direct cc: to the -rc announcements if you want me
to, to prevent this type of thing. Just let me know if you, or anyone
else, wants on them.
thanks,
greg k-h
next prev parent reply other threads:[~2021-01-30 11:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 11:06 [PATCH 4.9 00/30] 4.9.254-rc1 review Greg Kroah-Hartman
2021-01-29 11:06 ` [PATCH 4.9 19/30] bpf: Fix buggy rsh min/max bounds tracking Greg Kroah-Hartman
2021-01-29 18:22 ` [PATCH 4.9 00/30] 4.9.254-rc1 review Guenter Roeck
2021-01-29 19:08 ` Jon Hunter
2021-01-30 11:12 ` Jon Hunter
2021-01-30 11:52 ` Greg Kroah-Hartman [this message]
2021-01-30 13:52 ` Jon Hunter
2021-01-30 14:12 ` Greg Kroah-Hartman
2021-01-30 7:08 ` Naresh Kamboju
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=YBVIlENhvmBEndsU@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=pavel@denx.de \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).