From: Jean Delvare <jdelvare@suse.de>
To: monstr@monstr.eu
Cc: Mark Brown <broonie@kernel.org>,
netdev@vger.kernel.org, Nicolas Ferre <nicolas.ferre@atmel.com>,
Grant Likely <grant.likely@linaro.org>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v2] net: cadence: Add architecture dependencies
Date: Wed, 23 Apr 2014 12:48:38 +0200 [thread overview]
Message-ID: <20140423124838.37aa0759@endymion.delvare> (raw)
In-Reply-To: <5357897B.6020105@monstr.eu>
Hi Michal,
On Wed, 23 Apr 2014 11:35:55 +0200, Michal Simek wrote:
> On 04/23/2014 09:40 AM, Jean Delvare wrote:
> > Thanks for the information. I will send a patch adding MICROBLAZE to
> > the dependencies. Out of curiosity, is there any way I could have found
> > out by myself?
>
> Microblaze doesn't need to be only one. I am not sure if there is
> any AXI bridge for openrisc.
You lost me here again :-(
> IMHO you should just add COMPILE_TEST and do not try to extend that
> list of dependencies.
COMPILE_TEST is already present, I can't add it twice ;-) But
COMPILE_TEST isn't supposed to be used when the architecture /
platform / system is actually expected to possibly need the driver in
question. If the list of possible hardware dependencies isn't well
known, or is too complex to express, or too difficult to maintain, then
we have to either make it broader, or even drop it.
Originally I wanted to hide the Cadence drivers from X86 kernel
configuration. If there's still a way to achieve that, let's do it. If
not, we can leave the hardware dependency for ARM_AT91_ETHER and drop
the one for MACB (and subsequently NET_CADENCE.) That's still better
than nothing.
Please let me know how you want to proceed.
Thanks,
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2014-04-23 10:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 13:38 [PATCH v2] net: cadence: Add architecture dependencies Jean Delvare
2014-04-15 4:08 ` David Miller
2014-04-22 20:32 ` Mark Brown
2014-04-23 7:16 ` Michal Simek
2014-04-23 7:40 ` Jean Delvare
2014-04-23 9:35 ` Michal Simek
2014-04-23 10:48 ` Jean Delvare [this message]
2014-04-23 11:14 ` Michal Simek
2014-04-23 11:34 ` Mark Brown
2014-04-23 13:16 ` Michal Simek
2014-04-23 13:27 ` Jean Delvare
2014-04-23 14:23 ` Mark Brown
2014-04-23 11:27 ` Mark Brown
2014-04-23 10:04 ` Mark Brown
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=20140423124838.37aa0759@endymion.delvare \
--to=jdelvare@suse.de \
--cc=broonie@kernel.org \
--cc=grant.likely@linaro.org \
--cc=monstr@monstr.eu \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--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