From: Moritz Fischer <mdf@kernel.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Moritz Fischer <mdf@kernel.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, davem@davemloft.net,
alex.williams@ni.com, Rob Herring <robh+dt@kernel.org>
Subject: Re: [net-next RFC/PATCH] net: nixge: Make mdio child node optional
Date: Mon, 4 Feb 2019 08:34:17 -0800 [thread overview]
Message-ID: <20190204163417.GA2157@archbook> (raw)
In-Reply-To: <20190204145854.GD22111@lunn.ch>
On Mon, Feb 04, 2019 at 03:58:54PM +0100, Andrew Lunn wrote:
> On Fri, Feb 01, 2019 at 06:50:48PM -0800, Moritz Fischer wrote:
> > Make MDIO child optional and only instantiate the
> > MDIO bus if the child is actually present.
> >
> > There are currently no (in-tree) users of this
> > binding; all (out-of-tree) users use overlays that
> > get shipped together with the FPGA images that contain
> > the IP.
> >
> > This will significantly increase maintainabilty
> > of future revisions of this IP.
> >
> > Signed-off-by: Moritz Fischer <mdf@kernel.org>
> > Cc: Andrew Lunn <andrew@lunn.ch>
> > Cc: Rob Herring <robh+dt@kernel.org>
>
> Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Thanks.
>
> Andrew
I'll resubmit as a series together with the fixed-link change.
Since Dave has applied Alex' patches I'll need to rebase anyways,
otherwise it doesn't apply anymore to net-next.
Cheers,
Moritz
next prev parent reply other threads:[~2019-02-04 16:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-02 2:50 [net-next RFC/PATCH] net: nixge: Make mdio child node optional Moritz Fischer
2019-02-04 14:58 ` Andrew Lunn
2019-02-04 16:34 ` Moritz Fischer [this message]
2019-02-04 17:14 ` David Miller
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=20190204163417.GA2157@archbook \
--to=mdf@kernel.org \
--cc=alex.williams@ni.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@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).