From: Tony Lindgren <tony@atomide•com>
To: Peter Ujfalusi <peter.ujfalusi@ti•com>
Cc: bcousson@baylibre•com, linux-omap@vger•kernel.org,
devicetree@vger•kernel.org, linux-arm-kernel@lists•infradead.org,
nsekhar@ti•com, grygorii.strashko@ti•com, vkoul@kernel•org,
netdev@vger•kernel.org, f.fainelli@gmail•com,
marc.w.gonzalez@free•fr, niklas.cassel@linaro•org
Subject: Re: [PATCH 0/2] ARM: dts: am335x-evm/evmsk: Fix PHY mode for ethernet
Date: Tue, 19 Feb 2019 08:52:31 -0800 [thread overview]
Message-ID: <20190219165231.GK15711@atomide.com> (raw)
In-Reply-To: <c35030fb-9107-1919-5c18-1a39ace8c036@ti.com>
* Peter Ujfalusi <peter.ujfalusi@ti•com> [190219 08:02]:
> On 18/02/2019 18.26, Tony Lindgren wrote:
> > OK so sounds like these are OK to wait for v5.1 merge window
> > then as the dts changes alone won't fix anything?
>
> I think it would be better to send these to 5.0 to avoid the regression
> siting in linux-next.
>
> The patches are actually doing to the correct thing (we need rgmii-id,
> not rmgii-txid for these boards).
> It was just a matter of luck that it worked with rgmii-txid as the
> driver was broken and did not disabled the rxid when it should have.
OK applying into omap-for-v5.0/fixes-v2. I'll send a pull
request on Thursday most likely then, let's see if it makes
it for v5.0.
Regards,
Tony
next prev parent reply other threads:[~2019-02-19 16:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 14:36 [PATCH 0/2] ARM: dts: am335x-evm/evmsk: Fix PHY mode for ethernet Peter Ujfalusi
2019-02-18 14:36 ` [PATCH 1/2] ARM: dts: am335x-evmsk: " Peter Ujfalusi
2019-02-18 14:36 ` [PATCH 2/2] ARM: dts: am335x-evm: " Peter Ujfalusi
2019-02-18 14:44 ` [PATCH 0/2] ARM: dts: am335x-evm/evmsk: " Tony Lindgren
2019-02-18 16:22 ` Peter Ujfalusi
2019-02-18 16:26 ` Tony Lindgren
2019-02-19 8:02 ` Peter Ujfalusi
2019-02-19 16:52 ` Tony Lindgren [this message]
2019-02-20 8:30 ` Peter Ujfalusi
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=20190219165231.GK15711@atomide.com \
--to=tony@atomide$(echo .)com \
--cc=bcousson@baylibre$(echo .)com \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=f.fainelli@gmail$(echo .)com \
--cc=grygorii.strashko@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-omap@vger$(echo .)kernel.org \
--cc=marc.w.gonzalez@free$(echo .)fr \
--cc=netdev@vger$(echo .)kernel.org \
--cc=niklas.cassel@linaro$(echo .)org \
--cc=nsekhar@ti$(echo .)com \
--cc=peter.ujfalusi@ti$(echo .)com \
--cc=vkoul@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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