From: Leonard Crestez <leonard.crestez@nxp.com>
To: Florian Fainelli <f.fainelli@gmail.com>,
Shawn Guo <shawnguo@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
Andy Duan <fugang.duan@nxp.com>
Cc: Johan Hovold <johan@kernel.org>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>, <netdev@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] ARM: dts: imx6ul-14x14-evk: Add ksz8081 phy properties
Date: Wed, 31 May 2017 01:20:16 +0300 [thread overview]
Message-ID: <1496182816.19669.18.camel@nxp.com> (raw)
In-Reply-To: <46bde649-c9ce-5a87-d4c4-1c1ebc5a8923@gmail.com>
On Tue, 2017-05-30 at 11:10 -0700, Florian Fainelli wrote:
> On 05/30/2017 10:34 AM, Leonard Crestez wrote:
> > Right now mach-imx6ul registers a fixup for the ksz8081 phy. The same
> > register values can be set through the micrel phy driver by using dts
> > properties.
> >
> > This seems preferable and allows cleanly fixing suspend/resume.
> >
> > Signed-off-by: Leonard Crestez <leonard.crestez@nxp.com>
>
> Should you have a Fixes: tag for that? Sounds like something you'd want
> to backport to stable trees as well, no?
I don't know if suspend over nfs ever worked on this board in upstream
so there is no commit that this patch "Fixes: ". It would make sense to
CC stable.
next prev parent reply other threads:[~2017-05-30 22:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-30 17:34 [PATCH 0/2] ARM: imx6ul-14x14-evk: Fix suspend over nfs by phy cleanup Leonard Crestez
2017-05-30 17:34 ` [PATCH 1/2] ARM: dts: imx6ul-14x14-evk: Add ksz8081 phy properties Leonard Crestez
2017-05-30 18:10 ` Florian Fainelli
2017-05-30 22:20 ` Leonard Crestez [this message]
2017-05-31 4:08 ` Fabio Estevam
2017-05-30 17:34 ` [PATCH 2/2] net: phy: micrel: Restore led_mode and clk_sel on resume Leonard Crestez
2017-05-30 18:05 ` Florian Fainelli
2017-05-30 22:08 ` Leonard Crestez
2017-05-30 22:19 ` Florian Fainelli
2017-05-30 23:14 ` Leonard Crestez
2017-05-30 18:12 ` Fabio Estevam
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=1496182816.19669.18.camel@nxp.com \
--to=leonard.crestez@nxp.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=fabio.estevam@nxp.com \
--cc=fugang.duan@nxp.com \
--cc=johan@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).