netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joao Pinto <Joao.Pinto@synopsys.com>
To: David Miller <davem@davemloft.net>, <Joao.Pinto@synopsys.com>
Cc: <lars.persson@axis.com>, <niklass@axis.com>,
	<peppe.cavallaro@st.com>, <alexandre.torgue@st.com>,
	<netdev@vger.kernel.org>
Subject: Re: [PATCH] synopsys: remove dwc_eth_qos driver
Date: Thu, 12 Jan 2017 15:54:39 +0000	[thread overview]
Message-ID: <066a57f3-29b5-c297-cd67-d9c937b9c9d9@synopsys.com> (raw)
In-Reply-To: <20170112.104803.240247212224131685.davem@davemloft.net>

Às 3:48 PM de 1/12/2017, David Miller escreveu:
> From: Joao Pinto <Joao.Pinto@synopsys.com>
> Date: Thu, 12 Jan 2017 15:46:31 +0000
> 
>> Hope we can meet in a LinuxCon soon and have a talk, for you to know
>> me and this way you will see that I am a guy that is only focused in
>> producing work the best way possible, and nothing else.
> 
> I do not argue your intentions.
> 
> I argue the side effects of your change for the ecosystem of
> long term maintaince and backporting, and what tangible benefit
> this change brings to users.
> 

The driver synopsys/dwc_eth_qos is no longer necessary since it was ported to
stmmac. The merged followed all the requirements given by AXIS coleagues Niklas
and Lars. The new stmmac solution was tested by them. In my opinion of course
there is no reason to synopsys/dwc_eth_qos to exist anymore. I am deleting now a
synopsys/ name folder :) I did this work to improve organization and centralize
dwc ethernet in stmmac.

I know that changing what is working properly is a risk, I totally understand,
and if I was a top maintainer I would have the same concern of course. But in
this case I think it is good to organize the house. My intentions are to stick
around and help developing Ethernet, like I am helping developing PCI host/.

Thanks,
Joao

  reply	other threads:[~2017-01-12 15:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-12  9:56 [PATCH] synopsys: remove dwc_eth_qos driver Joao Pinto
2017-01-12 15:28 ` David Miller
2017-01-12 15:46   ` Joao Pinto
2017-01-12 15:48     ` David Miller
2017-01-12 15:54       ` Joao Pinto [this message]
2017-01-12 16:03         ` David Miller
2017-01-13  9:26         ` Niklas Cassel
2017-01-16  3:12 ` David Miller

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=066a57f3-29b5-c297-cd67-d9c937b9c9d9@synopsys.com \
    --to=joao.pinto@synopsys.com \
    --cc=alexandre.torgue@st.com \
    --cc=davem@davemloft.net \
    --cc=lars.persson@axis.com \
    --cc=netdev@vger.kernel.org \
    --cc=niklass@axis.com \
    --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;
as well as URLs for NNTP newsgroup(s).