mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joao Pinto <Joao.Pinto@synopsys.com>
To: David Miller <davem@davemloft.net>, <Joao.Pinto@synopsys.com>
Cc: <peppe.cavallaro@st.com>, <alexandre.torgue@st.com>,
	<netdev@vger.kernel>, <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] net: stmicro: eQOS IP Core
Date: Fri, 20 Jan 2017 17:27:45 +0000	[thread overview]
Message-ID: <e715ce49-769d-3098-cd04-46e435189fbc@synopsys.com> (raw)
In-Reply-To: <20170120.113447.2060254584042448007.davem@davemloft.net>

Às 4:34 PM de 1/20/2017, David Miller escreveu:
> From: Joao Pinto <Joao.Pinto@synopsys.com>
> Date: Fri, 20 Jan 2017 16:30:41 +0000
> 
>> Charade of renames? It is a bit strong, don't you agree?
> 
> Not at all.

To avoid this kind of "charade" comments, I sent an RFC, not an official patch
to be applied. Just a suggestion to be analysed by network/ developers.

> 
>> So you suggest to keep the driver called as dwmac4 when the IP is in fact eQOS?
>> Where do you suggest to put the eQOS 5.x features?
> 
> Since you are adding the new code, you can name the functions that implement
> eQOS 5.x support however you like.  You don't have to rename the dwmac4 code
> in order to add support for new chip families.
> 

The rename suggestion of the dwmac4_* files was because it is stating that they
are for a GMAC4 IP Core that does not exist. The controller is eQOS that started
in version 4.x and now is going to release a 5.x. My sugestion intention is to
put things clear and well structured to everyone that wish to use the driver in
the future.

I understand that you maintain a busy subsystem, and backport is a pain, but it
shouldn't avoid you improving its structure. You have duplicated drivers
targeting the same IPs and I just trying to puts things clear to avoid that in
the future.

I am going to focus developing the new features for the eQOS IP, and if sometime
you think about organizing or change the backport workflow I am available to
help you.

Joao Pinto

      reply	other threads:[~2017-01-20 17:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4584830fd1416af69ddb2e0168f78b1e343c33fe.1484914583.git.jpinto@synopsys.com>
     [not found] ` <20170120.112025.283503761726233382.davem@davemloft.net>
2017-01-20 16:30   ` Joao Pinto
2017-01-20 16:34     ` David Miller
2017-01-20 17:27       ` Joao Pinto [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=e715ce49-769d-3098-cd04-46e435189fbc@synopsys.com \
    --to=joao.pinto@synopsys.com \
    --cc=alexandre.torgue@st.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel \
    --cc=peppe.cavallaro@st.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®