From: Vinod Koul <vkoul@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, Linux Phy <linux-phy@lists.infradead.org>,
Kishon Vijay Abraham I <kishon@ti.com>
Subject: Re: Commits for 5.11 stable
Date: Tue, 2 Mar 2021 17:46:59 +0530 [thread overview]
Message-ID: <YD4su5gWILbbrd0z@vkoul-mobl> (raw)
In-Reply-To: <YD4WTn1mdE+RBoR1@kroah.com>
On 02-03-21, 11:41, Greg KH wrote:
> On Tue, Mar 02, 2021 at 03:55:27PM +0530, Vinod Koul wrote:
> >
> > HI Greg,
> >
> > On 02-03-21, 11:02, Greg KH wrote:
> > > On Tue, Mar 02, 2021 at 03:25:09PM +0530, Vinod Koul wrote:
> > > > Hi Greg,
> > > >
> > > > Please include these commits for 5.11 stable series
> > > >
> > > > 9a8b9434c60f phy: mediatek: Add missing MODULE_DEVICE_TABLE()
> > > > 25e3ee590f62 phy: phy-brcm-sata: remove unneeded semicolon
> > > > 6b46e60a6943 phy: USB_LGM_PHY should depend on X86
> > > > 36acd5e24e30 phy: lantiq: rcu-usb2: wait after clock enable
> > > > c188365402f6 phy: rockchip: emmc, add vendor prefix to dts properties
> > > > 88d9f40c4b71 devicetree: phy: rockchip-emmc optional add vendor prefix
> > > > aaf316de3bba phy: cpcap-usb: remove unneeded conversion to bool
> > > > 39961bd6b70e phy: rockchip-emmc: emmc_phy_init() always return 0
> > >
> > > Why take these?
> > >
> > > What problems do they solve?
> >
> > Sorry I should have provided the context. I had sent these as fixes for
> > 5.11 but that was bit late so we merged it for 5.12 [1]
>
> I still do not have any context :(
Please see the discussion we had in https://lore.kernel.org/lkml/20210210091249.GC2774@vkoul-mobl.Dlink/
> > > How does 25e3ee590f62 meet the stable tree rules?
Sorry it doesn't. My mistake on picking this for fixes. Lets drop this
one
> And all of these really are needed for stable? Again, how does this
> above commit qualify?
I relooked, expect this one, rest should be added for 5.11 stable.
Thanks
--
~Vinod
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2021-03-03 16:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 9:55 Commits for 5.11 stable Vinod Koul
2021-03-02 10:02 ` Greg KH
2021-03-02 10:25 ` Vinod Koul
2021-03-02 10:41 ` Greg KH
2021-03-02 12:16 ` Vinod Koul [this message]
2021-03-02 12:25 ` Greg KH
2021-03-05 10:30 ` Greg KH
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=YD4su5gWILbbrd0z@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kishon@ti.com \
--cc=linux-phy@lists.infradead.org \
--cc=stable@vger.kernel.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).