From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Pavel Machek <pavel@denx.de>,
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,
jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
paul.elder@ideasonboard.com
Subject: Re: [PATCH 4.14 00/20] 4.14.310-rc2 review
Date: Thu, 16 Mar 2023 10:23:49 +0100 [thread overview]
Message-ID: <ZBLgJfTDwqggdsJ6@kroah.com> (raw)
In-Reply-To: <0a3a9c3d-8d04-5b58-0f74-eb20759b1430@linaro.org>
On Thu, Mar 16, 2023 at 11:01:01AM +0200, Dmitry Baryshkov wrote:
> On 16/03/2023 11:00, Pavel Machek wrote:
> > (added patch authors to cc)
> >
> > > > This is the start of the stable review cycle for the 4.14.310 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.
> > >
> > > > Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> > > > clk: qcom: mmcc-apq8084: remove spdm clocks
> > >
> > > This looks like a cleanup, we should not need it in stable.
>
> Totally agree here.
Now dropped, thanks.
greg k-h
next prev parent reply other threads:[~2023-03-16 9:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 8:49 [PATCH 4.14 00/20] 4.14.310-rc2 review Greg Kroah-Hartman
2023-03-16 8:58 ` Pavel Machek
2023-03-16 9:00 ` Pavel Machek
2023-03-16 9:01 ` Dmitry Baryshkov
2023-03-16 9:23 ` Greg Kroah-Hartman [this message]
2023-03-16 9:23 ` Greg Kroah-Hartman
2023-03-16 11:25 ` Chris Paterson
2023-03-16 11:34 ` Greg Kroah-Hartman
2023-03-16 11:57 ` Chris Paterson
2023-03-16 12:01 ` Greg Kroah-Hartman
2023-03-16 22:53 ` Guenter Roeck
2023-03-17 2:48 ` 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=ZBLgJfTDwqggdsJ6@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=f.fainelli@gmail.com \
--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=paul.elder@ideasonboard.com \
--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 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.