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 15:12:52 +0100 [thread overview]
Message-ID: <YBVpZMtp0NWDaNca@kroah.com> (raw)
In-Reply-To: <1f078011-6a83-1954-7a37-56ca6cbc633f@nvidia.com>
On Sat, Jan 30, 2021 at 01:52:25PM +0000, Jon Hunter wrote:
>
> On 30/01/2021 11:52, Greg Kroah-Hartman wrote:
>
> ...
>
> > 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.
>
>
> Yes if you could add me to cc list that would be great.
Now added:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/commit/?id=2be9ba73cf0f6c3926f0d4caea60bb1feb141547
thanks,
greg k-h
next prev parent reply other threads:[~2021-01-30 14:15 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
2021-01-30 13:52 ` Jon Hunter
2021-01-30 14:12 ` Greg Kroah-Hartman [this message]
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=YBVpZMtp0NWDaNca@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.