From: Moritz Fischer <moritz.fischer.private@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Randy Dunlap <rdunlap@infradead.org>,
sfr@canb.auug.org.au, linux-next@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org
Subject: Re: linux-next: Tree for Aug 31 (nixge.c and phy)
Date: Fri, 31 Aug 2018 10:52:34 -0700 [thread overview]
Message-ID: <CAJYdmeOELPeG=xwkW5ODgQ+hVnHXFn6YOhtCaCdZS2z-uY2Uvw@mail.gmail.com> (raw)
In-Reply-To: <20180831175427.GC19733@lunn.ch>
Andrew,
On Fri, Aug 31, 2018 at 10:54 AM Andrew Lunn <andrew@lunn.ch> wrote:
>
> > @@ -20,7 +20,6 @@ config NI_XGE_MANAGEMENT_ENET
> > tristate "National Instruments XGE management enet support"
> > depends on HAS_IOMEM && HAS_DMA
> > select PHYLIB
> > - select OF_MDIO
> > help
> > Simple LAN device for debug or management purposes. Can
> > support either 10G or 1G PHYs via SFP+ ports.
>
> Hi Moritz
>
> Since you are targeting both DT and non-DT systems, you cannot
> unconditionally select OF_MDIO
>
> What might work is
>
> select OF_MDIO if OF
Sounds good. What's the process here? Follow-up patch to net-next?
Thanks again,
Moritz
next prev parent reply other threads:[~2018-08-31 18:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-31 3:03 linux-next: Tree for Aug 31 Stephen Rothwell
2018-08-31 15:43 ` linux-next: Tree for Aug 31 (drivers/usb/gadget/udc/renesas_usb3) Randy Dunlap
2018-09-03 3:20 ` Yoshihiro Shimoda
2018-08-31 15:57 ` linux-next: Tree for Aug 31 (nixge.c and phy) Randy Dunlap
2018-08-31 16:36 ` Moritz Fischer
2018-08-31 17:54 ` Andrew Lunn
2018-08-31 17:52 ` Moritz Fischer [this message]
2018-08-31 18:19 ` Andrew Lunn
2018-08-31 16:14 ` linux-next: Tree for Aug 31 (mix of ethernet and phy build errors) Randy Dunlap
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='CAJYdmeOELPeG=xwkW5ODgQ+hVnHXFn6YOhtCaCdZS2z-uY2Uvw@mail.gmail.com' \
--to=moritz.fischer.private@gmail.com \
--cc=andrew@lunn.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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).