All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Vineet Gupta <Vineet.Gupta1@synopsys.com>,
	Mischa Jonker <Mischa.Jonker@synopsys.com>,
	Grant Likely <grant.likely@linaro.org>,
	Rob Herring <rob.herring@calxeda.com>,
	Paul Gortmaker <paul.gortmaker@windriver.com>,
	"David S. Miller" <davem@davemloft.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"devicetree-discuss@lists.ozlabs.org"
	<devicetree-discuss@lists.ozlabs.org>
Subject: Re: [PATCH] ethernet/arc/arc_emac - Add new driver
Date: Fri, 07 Jun 2013 14:48:16 +0200	[thread overview]
Message-ID: <6204768.NxiQ5EdAsp@wuerfel> (raw)
In-Reply-To: <4881796E12491D4BB15146FE0209CE643F5C8E99@DE02WEMBXB.internal.synopsys.com>

On Friday 07 June 2013 12:37:24 Alexey Brodkin wrote:
> On 06/07/2013 04:13 PM, Arnd Bergmann wrote:
> >>> I wonder if it would be better to name the directory "synopsys" or
> >>> "designware" rather than "arc" now. Is there a chance that the same
> >>> controller is used on non-arc CPUs?
> >>
> >> The thing is - "arc_emac" is a custom ARC's (that was implemented before
> >> acquisition of ARC by Synopsys) IP (it's not an IC - just a part of CPU)
> >> Ethernet controller that only exists in some legacy FPGA boards we
> >> (ex-ARC and our customers) still use a lot in development process.
> >>
> >> Synopsys itself doesn't actively sell this device so there's no point in
> >> putting ARC EMAC into Synopsys folder.
> >>
> >> And indeed we don't expect this device to be used with non-ARC CPU's.
> 
> I'm wondering if my clarification above makes sense and I may leave this 
> driver in "ethernet/arc" or you still prefer it to be under 
> "ethernet/synopsys"?

Yes, I think if we don't expect any future Synopsys/Designware branded
devices to use this, using ethernet/arc is fine.

The main reason to still use a different name is so we will be able
to group it with other drivers for designware ethernet controllers.

The only one I'm currently aware of is drivers/net/ethernet/stmicro/stmmac/.
If we wanted to ahve a designware directory, we should probably move that
as well.

I'll leave it up to you (or Dave, if he has a strong opinion).

	Arnd

      reply	other threads:[~2013-06-07 12:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-04 12:21 [PATCH] ethernet/arc/arc_emac - Add new driver Alexey Brodkin
2013-06-04 12:21 ` Alexey Brodkin
     [not found] ` <1370348510-23754-1-git-send-email-abrodkin-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>
2013-06-06 23:35   ` David Miller
2013-06-06 23:35     ` David Miller
2013-06-07  8:47   ` Arnd Bergmann
2013-06-07  8:47     ` Arnd Bergmann
2013-06-07 10:42     ` Alexey Brodkin
2013-06-07 12:13       ` Arnd Bergmann
2013-06-07 12:37         ` Alexey Brodkin
2013-06-07 12:48           ` Arnd Bergmann [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=6204768.NxiQ5EdAsp@wuerfel \
    --to=arnd@arndb.de \
    --cc=Alexey.Brodkin@synopsys.com \
    --cc=Mischa.Jonker@synopsys.com \
    --cc=Vineet.Gupta1@synopsys.com \
    --cc=davem@davemloft.net \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=paul.gortmaker@windriver.com \
    --cc=rob.herring@calxeda.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.