netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Joao Pinto <Joao.Pinto@synopsys.com>
Cc: "Lars Persson" <lars.persson@axis.com>,
	"Giuseppe CAVALLARO" <peppe.cavallaro@st.com>,
	"Rayagond Kokatanur" <rayagond@vayavyalabs.com>,
	"Rabin Vincent" <rabin@rab.in>, "mued dib" <kreptor@gmail.com>,
	"David Miller" <davem@davemloft.net>,
	"Jeff Kirsher" <jeffrey.t.kirsher@intel.com>,
	"jiri@mellanox.com" <jiri@mellanox.com>,
	"saeedm@mellanox.com" <saeedm@mellanox.com>,
	"idosch@mellanox.com" <idosch@mellanox.com>,
	netdev <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"CARLOS.PALMINHA@synopsys.com" <CARLOS.PALMINHA@synopsys.com>,
	"Andreas Irestål" <andire@axis.com>,
	"alexandre.torgue@st.com" <alexandre.torgue@st.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: Synopsys Ethernet QoS Driver
Date: Wed, 7 Dec 2016 10:41:16 +0100	[thread overview]
Message-ID: <20161207094116.GA5399@amd> (raw)
In-Reply-To: <2eefdb8f-7e87-6009-6e50-c536d4b95dd6@synopsys.com>

[-- Attachment #1: Type: text/plain, Size: 660 bytes --]

Hi!

> > Thanks!
> 
> Regarding this subject, I am thinking of making the following adaption:
> 
> a) delete ethernet/synopsys
> b) rename ethernet/stmicro/stmmac to ethernet/synopsys
> 
> and send you a patch for you to evaluate. Both agree with the approach?
> To have a new work base would be important, because I will add to the "new"
> structure some missing QoS features like Multichannel support, CBS
> and later TSN.

Rename should be the easy part. Please do that last.

Thanks,
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  parent reply	other threads:[~2016-12-07  9:41 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CADvZ6ErjyVR5ShWTk0QesWLYR1m3p8yAMkK8v9gm2kN5xTv8zw@mail.gmail.com>
2016-11-18 14:20 ` Synopsys Ethernet QoS Driver Joao Pinto
2016-11-19 13:56   ` Rabin Vincent
2016-11-21  5:29     ` Rayagond Kokatanur
2016-11-21 12:32       ` Joao Pinto
2016-11-21 12:52         ` Giuseppe CAVALLARO
2016-11-21 13:28           ` Lars Persson
2016-11-21 14:25             ` Giuseppe CAVALLARO
2016-11-21 15:06               ` Joao Pinto
2016-11-21 15:43                 ` Lars Persson
2016-11-21 16:11                   ` Joao Pinto
2016-11-22 14:16                     ` Joao Pinto
2016-11-23 10:59                       ` Giuseppe CAVALLARO
2016-11-23 11:10                         ` Joao Pinto
2016-11-23 11:41                           ` Lars Persson
2016-11-23 11:43                             ` Joao Pinto
2016-11-25  8:55                               ` Giuseppe CAVALLARO
2016-12-07  9:41                       ` Pavel Machek [this message]
2016-11-21 13:48           ` Joao Pinto
2016-11-21 14:36             ` Giuseppe CAVALLARO
2016-11-21 15:00               ` Joao Pinto
2016-11-21 15:03                 ` Giuseppe CAVALLARO
2016-11-21 15:14                   ` Joao Pinto
2016-11-22  8:38               ` Ozgur Karatas
2016-11-23  8:02                 ` Giuseppe CAVALLARO
2016-12-07 20:15           ` Andy Shevchenko
2016-11-18 12:28 Joao Pinto
2016-11-18 12:31 ` Joao Pinto
2016-11-18 14:53 ` Florian Fainelli
2016-11-18 16:31   ` Joao Pinto
2016-11-18 16:35     ` Florian Fainelli
2016-11-18 16:40       ` Joao Pinto
2016-11-18 18:29         ` Eric Dumazet

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=20161207094116.GA5399@amd \
    --to=pavel@ucw.cz \
    --cc=CARLOS.PALMINHA@synopsys.com \
    --cc=Joao.Pinto@synopsys.com \
    --cc=alexandre.torgue@st.com \
    --cc=andire@axis.com \
    --cc=davem@davemloft.net \
    --cc=idosch@mellanox.com \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=jiri@mellanox.com \
    --cc=kreptor@gmail.com \
    --cc=lars.persson@axis.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=peppe.cavallaro@st.com \
    --cc=rabin@rab.in \
    --cc=rayagond@vayavyalabs.com \
    --cc=saeedm@mellanox.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).