public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Shawn Guo <shawnguo@kernel.org>
Cc: Aisheng Dong <aisheng.dong@nxp.com>, Andrew Lunn <andrew@lunn.ch>,
	dl-linux-imx <linux-imx@nxp.com>,
	"kernel@pengutronix.de" <kernel@pengutronix.de>,
	Leonard Crestez <leonard.crestez@nxp.com>,
	Fabio Estevam <festevam@gmail.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] i.MX fixes for 5.1, round 3
Date: Thu, 16 May 2019 14:50:30 -0700	[thread overview]
Message-ID: <20190516215030.bzmsdcu5524lskki@localhost> (raw)
In-Reply-To: <20190507083218.GB22736@dragon>

On Tue, May 07, 2019 at 04:32:20PM +0800, Shawn Guo wrote:
> On Mon, May 06, 2019 at 07:10:22PM +0000, Leonard Crestez wrote:
> > On 4/22/19 6:19 AM, Shawn Guo wrote:
> > > The following changes since commit 7aedca875074b33795bc77066b325898b1eb8032:
> > > 
> > >    ARM: dts: imx6q-logicpd: Reduce inrush current on USBH1 (2019-04-11 13:45:03 +0800)
> > > 
> > > are available in the Git repository at:
> > > 
> > >    git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-fixes-5.1-3
> > > 
> > > for you to fetch changes up to c7861adbe37f576931650ad8ef805e0c47564b9a:
> > > 
> > >    ARM: dts: ls1021: Fix SGMII PCS link remaining down after PHY disconnect (2019-04-21 15:51:28 +0800)
> > 
> > I am confused by the path these fixes take to Linus.
> > 
> > The rgmii DT fixes from commit 0672d22a1924 ("ARM: dts: imx: Fix the 
> > AR803X phy-mode") are still not present in v5.1 and netboot fails on a 
> > large number of imx6 sabresd boards which have been stable for quite a 
> > while.
> > 
> > These should have been included from "round 2": 
> > https://www.spinics.net/lists/arm-kernel/msg723998.html
> 
> Unfortunately, we did have both round 2 and 3 miss 5.1 release.
> 
> @Olof, on April 28 you said you merged them.  What happened there?
> 
> I guess the only thing we can do is to merge them into v5.2-rc1 and get
> them back onto v5.1.x stable kernel then.  Most of the patches have
> Fixes tag and thus will be picked by Greg to v5.1.x.  But the one that
> Leonard is talking about doesn't have.  @Fabio, can you please help send
> it to Greg for v5.1.x inclusion?

Yeah, they should be picked up for stable. For the one not labeled with
a Fixes-tag, see Documentation/process/stable-kernel-rules.rst.


-Olof

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-05-16 21:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-22  3:19 [GIT PULL] i.MX fixes for 5.1, round 3 Shawn Guo
2019-04-28 20:26 ` Olof Johansson
2019-05-06 19:10 ` Leonard Crestez
2019-05-07  8:32   ` Shawn Guo
2019-05-16 21:50     ` Olof Johansson [this message]
2019-05-16 23:41       ` Olof Johansson

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=20190516215030.bzmsdcu5524lskki@localhost \
    --to=olof@lixom.net \
    --cc=aisheng.dong@nxp.com \
    --cc=andrew@lunn.ch \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=leonard.crestez@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=shawnguo@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