From: David Miller <davem@davemloft.net>
To: 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 10:26:30 -0500 (EST) [thread overview]
Message-ID: <20170112.102630.1448382649844350511.davem@davemloft.net> (raw)
In-Reply-To: <dbb59d07-4ab4-37d2-5e70-073091749445@synopsys.com>
I don't understand at all why it is so important to change the name of
these files nor the directory they live in.
What bonafide benefit will users receive if we do this?
The only clear part is the downside, which is that it is going to make
it painful to browse source history and backport bug fixes.
Please, let's not do this.
Thanks.
next prev parent reply other threads:[~2017-01-12 15:26 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 [this message]
2017-01-12 15:39 ` Joao Pinto
2017-01-12 15:45 ` David Miller
2017-01-12 16:04 ` Joao Pinto
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=20170112.102630.1448382649844350511.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Joao.Pinto@synopsys.com \
--cc=alexandre.torgue@st.com \
--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).