[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFBinCB3SLoVOt_jy6-OW=2=5671o+bXQwMn006u56gHLTOpBw@mail.gmail.com>
Date: Mon, 10 Jun 2019 00:32:52 +0200
From: Martin Blumenstingl <martin.blumenstingl@...glemail.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: netdev@...r.kernel.org, linux-gpio@...r.kernel.org,
linux-amlogic@...ts.infradead.org, linus.walleij@...aro.org,
bgolaszewski@...libre.com, peppe.cavallaro@...com,
alexandre.torgue@...com, joabreu@...opsys.com,
devicetree@...r.kernel.org,
Neil Armstrong <narmstrong@...libre.com>, khilman@...libre.com,
linux-kernel@...r.kernel.org, davem@...emloft.net,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [RFC next v1 0/5] stmmac: honor the GPIO flags for the PHY reset GPIO
Hi Andrew,
On Sun, Jun 9, 2019 at 10:45 PM Andrew Lunn <andrew@...n.ch> wrote:
>
> > Patch #1 and #4 are minor cleanups which follow the boyscout rule:
> > "Always leave the campground cleaner than you found it."
>
> > I
> > am also looking for suggestions how to handle these cross-tree changes
> > (patch #2 belongs to the linux-gpio tree, patches #1, 3 and #4 should
> > go through the net-next tree. I will re-send patch #5 separately as
> > this should go through Kevin's linux-amlogic tree).
>
> Hi Martin
>
> Patches 1 and 4 don't seem to have and dependencies. So i would
> suggest splitting them out and submitting them to netdev for merging
> independent of the rest.
OK, I will do that but after the GPIO changes are applied because only
then I can get rid of that "np" variable
> Linus can probably create a stable branch with the GPIO changes, which
> David can pull into net-next, and then apply the stmmac changes on
> top.
let's go this way since Linus is happy with that route also.
I'll re-spin v2 tomorrow
Martin
Powered by blists - more mailing lists