All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Russell King - ARM Linux <linux@armlinux.org.uk>,
	Soeren Moch <smoch@web.de>,
	Steve Twiss <stwiss.opensource@diasemi.com>,
	NXP Linux Team <linux-imx@nxp.com>,
	Sascha Hauer <kernel@pengutronix.de>,
	Shawn Guo <shawnguo@kernel.org>,
	"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC] ARM: dts: imx: Fix the AR803X phy-mode
Date: Mon, 1 Apr 2019 09:53:19 -0300	[thread overview]
Message-ID: <CAOMZO5CFe-A_=9VUY==6sN0CjN=EsaVFYov4p-hzrAB-pw7tUw@mail.gmail.com> (raw)
In-Reply-To: <20190330161814.GB32667@lunn.ch>

Hi Andrew,

On Sat, Mar 30, 2019 at 1:18 PM Andrew Lunn <andrew@lunn.ch> wrote:
>
> > Hi,
> >
> > Marking it as RFC in the hope of getting some feedback as to how
> > to proceed with fixing this regression on 5.1-rc1.
>
> I think it should be safe to propose these patches go to stable.
>
> RGMII-ID has been supported since
>
> 2e5f9f281ee8 ("net: phy: at803x: Allow specifying the RGMII RX clock delay via phy mode")
>
> Which is somewhere around v4.4. So back porting them should be fine.

This commit landed in v4.5, so I marked it as:
Cc: <stable@vger.kernel.org> # 4.9+

I probably will need to manually generate versions for the some of the
stable versions.

Thanks

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

  reply	other threads:[~2019-04-01 12:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-30 15:50 [RFC] ARM: dts: imx: Fix the AR803X phy-mode Fabio Estevam
2019-03-30 16:18 ` Andrew Lunn
2019-04-01 12:53   ` Fabio Estevam [this message]
2019-03-30 19:06 ` Baruch Siach
2019-03-30 19:11   ` Fabio Estevam
2019-03-31  3:50     ` Baruch Siach
2019-03-31 10:44 ` Soeren Moch
2019-04-01  8:38 ` Steve Twiss
2019-04-01  8:38   ` Steve Twiss
2019-04-01 12:48   ` Fabio Estevam
2019-04-01 12:48     ` Fabio Estevam
2019-04-01  9:01 ` Sébastien Szymanski
2019-04-01  9:05 ` Marc Kleine-Budde

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='CAOMZO5CFe-A_=9VUY==6sN0CjN=EsaVFYov4p-hzrAB-pw7tUw@mail.gmail.com' \
    --to=festevam@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux@armlinux.org.uk \
    --cc=shawnguo@kernel.org \
    --cc=smoch@web.de \
    --cc=stwiss.opensource@diasemi.com \
    /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.