From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Pavel Machek <pavel@denx.de>
Cc: 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,
stable@vger.kernel.org
Subject: Re: [PATCH 4.4 00/20] 4.4.250-rc2 review
Date: Thu, 7 Jan 2021 18:55:30 +0100 [thread overview]
Message-ID: <X/dLEsU/0BN42UQ7@kroah.com> (raw)
In-Reply-To: <20210107163039.GB9524@duo.ucw.cz>
On Thu, Jan 07, 2021 at 05:30:39PM +0100, Pavel Machek wrote:
> Hi!
>
> > This is the start of the stable review cycle for the 4.4.250 release.
> > There are 20 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 Sat, 09 Jan 2021 14:30:35 +0000.
> > Anything received after that time might be too late.
>
> This and 4.19.166-rc1 was tested by CIP project, and we did not find
> anything wrong.
>
> https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/tree/linux-4.4.y
> https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/tree/linux-4.19.y
>
> (I'm sending one email instead of two to keep the traffic down. If you
> prefer separate emails, let me know.)
>
> Tested-by: Pavel Machek (CIP) <pavel@denx.de>
Separate is better as that's how I pick up the tested-by tags for the
release commits.
thanks,
greg k-h
next prev parent reply other threads:[~2021-01-07 17:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 14:31 [PATCH 4.4 00/20] 4.4.250-rc2 review Greg Kroah-Hartman
2021-01-07 16:30 ` Pavel Machek
2021-01-07 17:55 ` Greg Kroah-Hartman [this message]
2021-01-07 20:20 ` Jon Hunter
2021-01-08 1:13 ` Shuah Khan
2021-01-08 8:05 ` Naresh Kamboju
2021-01-08 17:37 ` Guenter Roeck
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=X/dLEsU/0BN42UQ7@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@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