From: Joao Pinto <Joao.Pinto@synopsys.com>
To: David Miller <davem@davemloft.net>, <Joao.Pinto@synopsys.com>
Cc: <peppe.cavallaro@st.com>, <lars.persson@axis.com>,
<rabin.vincent@axis.com>, <netdev@vger.kernel.org>,
<andy.shevchenko@gmail.com>, <CARLOS.PALMINHA@synopsys.com>
Subject: Re: Synopsys Ethernet QoS
Date: Fri, 9 Dec 2016 15:54:00 +0000 [thread overview]
Message-ID: <f5029f0c-1a74-7b24-327e-ab1dce020954@synopsys.com> (raw)
In-Reply-To: <20161209.104152.1969880574279771010.davem@davemloft.net>
Às 3:41 PM de 12/9/2016, David Miller escreveu:
> From: Joao Pinto <Joao.Pinto@synopsys.com>
> Date: Fri, 9 Dec 2016 15:36:38 +0000
>
>> Of course, I started a general discussion about the subject and
>> those were the conclusions, but I would like to know if you as the
>> subsystem maintainer also support the approach or have any
>> suggestion.
>
> Generally, I support whatever the interested parties agree to.
>
> But one thing I am against is changing the driver name for existing
> users. If an existing chip is supported by the stmmac driver for
> existing users, they should still continue to use the "stmmac" driver.
>
> Therefore, if consolidation changes the driver module name for
> existing users, then that is not a good plan at all.
>
Of course, 100% with you! Retro-compatibility for existing drivers is a must
have. The consolidation is going to be done with extreme careful.
Joao
next prev parent reply other threads:[~2016-12-09 15:54 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-09 11:29 Synopsys Ethernet QoS Joao Pinto
2016-12-09 15:33 ` David Miller
2016-12-09 15:36 ` Joao Pinto
2016-12-09 15:41 ` David Miller
2016-12-09 15:54 ` Joao Pinto [this message]
2016-12-09 22:25 ` Andy Shevchenko
2016-12-09 22:52 ` Florian Fainelli
2016-12-10 0:16 ` Andy Shevchenko
2016-12-10 1:44 ` Florian Fainelli
2016-12-12 10:19 ` Joao Pinto
2016-12-12 14:11 ` Giuseppe CAVALLARO
2016-12-12 16:25 ` Niklas Cassel
2016-12-12 16:46 ` Stephen Warren
2016-12-13 7:22 ` Giuseppe CAVALLARO
2016-12-13 9:38 ` Niklas Cassel
2016-12-13 9:51 ` Giuseppe CAVALLARO
2016-12-14 12:57 ` Pavel Machek
2016-12-14 13:14 ` Joao Pinto
2016-12-14 19:01 ` stmmac: lockups (was Re: Synopsys Ethernet QoS) Pavel Machek
2016-12-15 11:09 ` Synopsys Ethernet QoS Pavel Machek
2016-12-17 17:38 ` Pavel Machek
2016-12-19 10:55 ` Joao Pinto
2016-12-19 11:01 ` Joao Pinto
2016-12-15 12:05 ` Niklas Cassel
2016-12-19 17:58 ` Niklas Cassel
2016-12-13 11:49 ` Joao Pinto
2016-12-13 12:31 ` Niklas Cassel
2016-12-13 12:50 ` Lars Persson
2016-12-13 12:56 ` Joao Pinto
2016-12-19 16:05 ` Niklas Cassel
2016-12-14 11:54 ` Pavel Machek
2016-12-10 2:13 ` Jie Deng
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=f5029f0c-1a74-7b24-327e-ab1dce020954@synopsys.com \
--to=joao.pinto@synopsys.com \
--cc=CARLOS.PALMINHA@synopsys.com \
--cc=andy.shevchenko@gmail.com \
--cc=davem@davemloft.net \
--cc=lars.persson@axis.com \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.com \
--cc=rabin.vincent@axis.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.