From: Joao Pinto <Joao.Pinto@synopsys.com>
To: David Miller <davem@davemloft.net>, <Joao.Pinto@synopsys.com>
Cc: <alexandre.torgue@st.com>, <f.fainelli@gmail.com>,
<lars.persson@axis.com>, <niklass@axis.com>,
<peppe.cavallaro@st.com>, <netdev@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] stmmac: rename it to synopsys
Date: Thu, 12 Jan 2017 16:04:45 +0000 [thread overview]
Message-ID: <6da8254b-11b2-aa0d-9640-ca73e30bcc0f@synopsys.com> (raw)
In-Reply-To: <20170112.104539.326369092090046644.davem@davemloft.net>
Às 3:45 PM de 1/12/2017, David Miller escreveu:
> From: Joao Pinto <Joao.Pinto@synopsys.com>
> Date: Thu, 12 Jan 2017 15:39:47 +0000
>
>> In my understanding the advantage is to prepare the future.
>
> If the driver is named foo or bar, yet in both cases loads and
> properly attaches to the user's device, the user does not care.
Of course. Although my car works I like to open the hood a see it clean and
organized. Gives the user more confidence.
>
> Therefore, there is no bonafide benefit to the user.
>
> You aren't getting past that point.
>
> You also are not addressing the pain this will cause for long
> term maintainence of this driver.
I am aware. I can co-maintain it if current maintainers wish it, no problem with
that. My activity at Synopsys in mainline contribution, so it is part of my job.
>
> I'm the one who does all of the backporting of stmmac bug fixes to
> -stable, so I for one care a lot about this.
>
> You are making more work for me and lots of other people by renaming
> this driver and I don't think you are considering that at all.
>
I understand, it is a lot of work. I volunteer to help.
Joao
next prev parent reply other threads:[~2017-01-12 16:04 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 14:52 [PATCH v2 0/2] remove dwc_eth_qos and rename stmicro/stmmac Joao Pinto
2017-01-10 14:52 ` [PATCH v2 1/2] synopsys: remove dwc_eth_qos driver Joao Pinto
2017-01-10 15:15 ` Lars Persson
2017-01-10 14:52 ` [PATCH v2 2/2] stmmac: rename it to synopsys Joao Pinto
2017-01-11 4:00 ` Jie Deng
2017-01-11 10:35 ` Joao Pinto
2017-01-12 3:44 ` Jie Deng
2017-01-12 5:05 ` Florian Fainelli
2017-01-11 10:00 ` kbuild test robot
2017-01-11 21:14 ` Florian Fainelli
2017-01-11 21:32 ` David Miller
2017-01-12 9:43 ` Joao Pinto
2017-01-12 10:11 ` Alexandre Torgue
2017-01-12 11:09 ` Joao Pinto
2017-01-12 15:26 ` David Miller
2017-01-12 15:39 ` Joao Pinto
2017-01-12 15:45 ` David Miller
2017-01-12 16:04 ` Joao Pinto [this message]
2017-01-12 19:42 ` Florian Fainelli
2017-01-13 11:20 ` Joao Pinto
2017-01-11 11:39 ` [PATCH v2 0/2] remove dwc_eth_qos and rename stmicro/stmmac Alexandre Torgue
2017-01-11 11:54 ` Joao Pinto
2017-01-11 14:25 ` Alexandre Torgue
2017-01-11 14:29 ` Joao Pinto
2017-01-11 14:39 ` Alexandre Torgue
2017-01-11 14:54 ` Joao Pinto
2017-01-11 14:52 ` David Miller
2017-01-11 15:06 ` Joao Pinto
2017-01-11 15:20 ` David Miller
2017-01-11 16:17 ` Joao Pinto
2017-01-11 16:19 ` Joao Pinto
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=6da8254b-11b2-aa0d-9640-ca73e30bcc0f@synopsys.com \
--to=joao.pinto@synopsys.com \
--cc=alexandre.torgue@st.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--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).