linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Jeroen Hofstee <jhofstee@victronenergy.com>
Cc: "Grygorii Strashko" <grygorii.strashko@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"Koen Kooi" <koen@dominion.thruhere.net>,
	"Benoît Cousson" <bcousson@baylibre.com>,
	"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: dts: am335x-sancloud-bbe: Fix PHY mode for ethernet
Date: Tue, 8 Oct 2019 10:02:59 -0700	[thread overview]
Message-ID: <20191008170259.GI5610@atomide.com> (raw)
In-Reply-To: <a8a72544-7f30-c896-22e4-7d85bd0b4235@victronenergy.com>

* Jeroen Hofstee <jhofstee@victronenergy.com> [191008 17:00]:
> Hi,
> 
> On 10/8/19 6:51 PM, Tony Lindgren wrote:
> > * Jeroen Hofstee <jhofstee@victronenergy.com> [191008 16:43]:
> >> Hello Tony,
> >>
> >> On 10/8/19 6:14 PM, Tony Lindgren wrote:
> >>> * Jeroen Hofstee <jhofstee@victronenergy.com> [191008 16:03]:
> >>>> Hello Tony,
> >>>>
> >>>> On 10/8/19 4:23 PM, Tony Lindgren wrote:
> >>>>> * Grygorii Strashko <grygorii.strashko@ti.com> [191003 02:32]:
> >>>>>> On 03/10/2019 11:16, Jeroen Hofstee wrote:
> >>>>>>> Furthermore 4.19 is fine, so there is no need to include it in stable
> >>>>>>> and have a note to make sure also other patches are required etc.
> >>>>>> Hence all above patches went in 5.1 it would be correct to mention only
> >>>>>> 6d4cd041f0af net: phy: at803x: disable delay only for RGMII mode
> >>>>> Jeroen, can you please send an updated patch with the fixes
> >>>>> tag changed?
> >>>>>
> >>>> For completeness, there is no "Fixes tag" as you mentioned.
> >>>> The commit only refers to another commit which introduces
> >>>> a problem.
> >>> Well please add the fixes tag, that way this will get
> >>> properly applied to earlier stable kernels too :)
> >> But 4.19 is fine, this is an issue in 5.1 as in EOL...
> >> I really don't understand why I should waste time
> >> to figure out what happened exactly during the 5.1
> >> release cycle...
> > Hmm so what's the issue with just adding the fixes tag Grygorii
> > suggested:
> >
> > 6d4cd041f0af ("net: phy: at803x: disable delay only for RGMII mode")
> >
> > No need to dig further?
> 
> Grygorii doesn't suggest to add a fixes tag, just to change the referenced
> commit to another. Obviously I would like to understand why another commit
> should be referenced. And then I should read and parse the response, so there
> is no special reason, just time...

OK sure. Well once you guys have the commit figured out, let me
know what to apply. And we know Grygorii is mostly right based
on his history of comments so best to not ignore that :)

Cheers,

Tony

  reply	other threads:[~2019-10-08 17:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-02  9:54 [PATCH] ARM: dts: am335x-sancloud-bbe: Fix PHY mode for ethernet Jeroen Hofstee
2019-10-02 14:48 ` Grygorii Strashko
2019-10-03  8:16   ` Jeroen Hofstee
2019-10-03  9:31     ` Grygorii Strashko
2019-10-08 14:23       ` Tony Lindgren
2019-10-08 14:46         ` Jeroen Hofstee
2019-10-08 16:02         ` Jeroen Hofstee
2019-10-08 16:14           ` Tony Lindgren
2019-10-08 16:42             ` Jeroen Hofstee
2019-10-08 16:51               ` Tony Lindgren
2019-10-08 16:59                 ` Jeroen Hofstee
2019-10-08 17:02                   ` Tony Lindgren [this message]
2019-10-09  9:43                     ` Grygorii Strashko
2019-10-09 10:09                       ` Jeroen Hofstee

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=20191008170259.GI5610@atomide.com \
    --to=tony@atomide.com \
    --cc=bcousson@baylibre.com \
    --cc=grygorii.strashko@ti.com \
    --cc=jhofstee@victronenergy.com \
    --cc=koen@dominion.thruhere.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@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).