From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] ARM: shmobile: sh-eth pins in DT for armadillo800eva
Date: Fri, 25 Jan 2013 09:05:44 +0000 [thread overview]
Message-ID: <20130125090544.GD30990@verge.net.au> (raw)
In-Reply-To: <Pine.LNX.4.64.1301250856040.17518@axis700.grange>
On Fri, Jan 25, 2013 at 09:09:54AM +0100, Guennadi Liakhovetski wrote:
> Hi Simon
>
> On Fri, 25 Jan 2013, Simon Horman wrote:
>
> > On Thu, Jan 24, 2013 at 05:07:30PM +0100, Guennadi Liakhovetski wrote:
> > > This patch series gets rid of gpio_request()-style ethernet pin
> > > configuration on armadillo800eva in reference implementation.
> >
> > Hi Guennadi,
> >
> > these changes seem to be reasonable to me.
> >
> > Are there any dependencies for the sh_eth patch?
> > I assume this will be handled by David Miller through the net-next tree.
> > Are there any dependencies? The last time I checked the DT bindings
> > for sh_eth had not been merged.
>
> Obviously, it can only be applied, if the
> Documentation/devicetree/bindings/net/sh_ether.txt file and the
> sh_eth_parse_dt() function exist. Also, if there are no objections against
> the new phy-reset-gpios DT property. Otherwise there are no dependencies -
> as long as the phy-reset-gpios property isn't found in DT, the patch
> doesn't affect the driver.
Thanks, I'm slightly concerned that the other patch(es) relating
to Documentation/devicetree/bindings/net/sh_ether.txt have gone missing in
action.
Do you have an interest in chasing them down or would you like me to?
> > For the remaining two patches, which I assume will go through my renesas
> > tree:
> > * Are there any dependencies that aren't satisfied by the of-intc branch?
>
> AFAICS, that your branch doesn't contain Laurent's pinctrl patches, which
> are needed for patch 1 to apply and for patch 3 to make sense. My earlier
> MMC DT / pinctrl patches aren't required for these patches to function,
> but these patches won't apply cleanly without them, since they touch the
> same code fragments. So, it would be easier to merge them in the order of
> submission.
>
> > * Could you get some Acks. At least from Laurent?
>
> Sure, let's give reviewers some more time :)
Indeed.
Laurent, if there are patches ready for me to take into the renesas tree
please let me know. I'm reluctant to add any more pinmux changes for 3.9.
But if a topic branch would help let me know.
next prev parent reply other threads:[~2013-01-25 9:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 16:07 [PATCH 0/3] ARM: shmobile: sh-eth pins in DT for armadillo800eva Guennadi Liakhovetski
2013-01-24 16:07 ` [PATCH 1/3] pinctrl: add ethernet pin groups to r8a7740 Guennadi Liakhovetski
2013-01-25 10:15 ` Laurent Pinchart
2013-01-24 16:07 ` [PATCH/RFC 2/3] ethernet: add a PHY reset GPIO DT binding to sh_eth Guennadi Liakhovetski
2013-01-25 10:21 ` Laurent Pinchart
2013-01-25 10:34 ` Guennadi Liakhovetski
2013-01-25 18:21 ` Jason Gunthorpe
2013-07-08 10:49 ` Guennadi Liakhovetski
2013-01-26 1:04 ` Laurent Pinchart
2013-01-24 16:07 ` [PATCH 3/3] ARM: shmobile: move pin configuration on armadillo800eva-reference to DT Guennadi Liakhovetski
2013-01-25 4:37 ` [PATCH 0/3] ARM: shmobile: sh-eth pins in DT for armadillo800eva Simon Horman
2013-01-25 8:09 ` Guennadi Liakhovetski
2013-01-25 9:05 ` Simon Horman [this message]
2013-01-25 9:57 ` Laurent Pinchart
2013-01-28 1:02 ` Simon Horman
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=20130125090544.GD30990@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.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).