From: Geert Uytterhoeven <geert@linux-m68k.org>
To: David Miller <davem@davemloft.net>
Cc: Tony Prisk <linux@prisktech.co.nz>,
netdev <netdev@vger.kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] via-rhine: Add platform dependencies
Date: Fri, 8 May 2020 09:10:20 +0200 [thread overview]
Message-ID: <CAMuHMdWKp5X3VsiHHFxaVgenmx=M8ScP98Lqu+DoavWGJhowLQ@mail.gmail.com> (raw)
In-Reply-To: <20200507.131727.907589220898369492.davem@davemloft.net>
Hi David,
On Thu, May 7, 2020 at 10:17 PM David Miller <davem@davemloft.net> wrote:
> From: Geert Uytterhoeven <geert+renesas@glider.be>
> Date: Thu, 7 May 2020 13:42:05 +0200
>
> > The VIA Rhine Ethernet interface is only present on PCI devices or
> > VIA/WonderMedia VT8500/WM85xx SoCs. Add platform dependencies to the
> > VIA_RHINE config symbol, to avoid asking the user about it when
> > configuring a kernel without PCI or VT8500/WM85xx support.
> >
> > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
>
> Applied to net-next.
Thank you!
> Although I hope that the COMPILE_TEST guard is not too loose and
> now we'll have randconfig build failures for some reason.
I only added a dependency line, and didn't replace the old one.
The "depends on PCI || (OF_IRQ && GENERIC_PCI_IOMAP)" is still there.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-05-08 7:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 11:42 [PATCH] via-rhine: Add platform dependencies Geert Uytterhoeven
2020-05-07 13:19 ` Arnd Bergmann
2020-05-07 20:17 ` David Miller
2020-05-08 7:10 ` Geert Uytterhoeven [this message]
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='CAMuHMdWKp5X3VsiHHFxaVgenmx=M8ScP98Lqu+DoavWGJhowLQ@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=geert+renesas@glider.be \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@prisktech.co.nz \
--cc=netdev@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).