All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Giuseppe CAVALLARO <peppe.cavallaro@st.com>
Cc: Joao Pinto <Joao.Pinto@synopsys.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, saeedm@mellanox.com, idosch@mellanox.com,
	netdev <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	CARLOS.PALMINHA@synopsys.com, andreas.irestal@axis.com,
	lars.persson@axis.com, Alexandre TORGUE <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 22:15:55 +0200	[thread overview]
Message-ID: <CAHp75Vf2ZncJcGguueh2fCsHaZVin8qGSk+hDUt+uRg8ffgZbQ@mail.gmail.com> (raw)
In-Reply-To: <87c8a24b-0812-7850-cb3f-7be691bab432@st.com>

On Mon, Nov 21, 2016 at 2:52 PM, Giuseppe CAVALLARO
<peppe.cavallaro@st.com> wrote:

First of all, +1 to (re-)use stmmac.

> The stmmac drivers run since many years on several platforms
> (sh4, stm32, arm, x86, mips ...) and it supports an huge of amount of
> configurations starting from 3.1x to 3.7x databooks.

As Intel employee who did some clean ups to that, acknowledge above.

> Concerning the stmicro/stmmac naming, these come from a really old
> story and have no issue to adopt new folder/file names.

I don't think it would be best idea for platform driver (though we can
keep driver's name in the structure in async with file name).

-- 
With Best Regards,
Andy Shevchenko

WARNING: multiple messages have this Message-ID (diff)
From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Giuseppe CAVALLARO <peppe.cavallaro@st.com>
Cc: idosch@mellanox.com, Joao Pinto <Joao.Pinto@synopsys.com>,
	andreas.irestal@axis.com,
	Alexandre TORGUE <alexandre.torgue@st.com>,
	saeedm@mellanox.com, netdev <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	CARLOS.PALMINHA@synopsys.com, Rabin Vincent <rabin@rab.in>,
	mued dib <kreptor@gmail.com>,
	jiri@mellanox.com, Rayagond Kokatanur <rayagond@vayavyalabs.com>,
	Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
	David Miller <davem@davemloft.net>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	lars.persson@axis.com
Subject: Re: Synopsys Ethernet QoS Driver
Date: Wed, 7 Dec 2016 22:15:55 +0200	[thread overview]
Message-ID: <CAHp75Vf2ZncJcGguueh2fCsHaZVin8qGSk+hDUt+uRg8ffgZbQ@mail.gmail.com> (raw)
In-Reply-To: <87c8a24b-0812-7850-cb3f-7be691bab432@st.com>

On Mon, Nov 21, 2016 at 2:52 PM, Giuseppe CAVALLARO
<peppe.cavallaro@st.com> wrote:

First of all, +1 to (re-)use stmmac.

> The stmmac drivers run since many years on several platforms
> (sh4, stm32, arm, x86, mips ...) and it supports an huge of amount of
> configurations starting from 3.1x to 3.7x databooks.

As Intel employee who did some clean ups to that, acknowledge above.

> Concerning the stmicro/stmmac naming, these come from a really old
> story and have no issue to adopt new folder/file names.

I don't think it would be best idea for platform driver (though we can
keep driver's name in the structure in async with file name).

-- 
With Best Regards,
Andy Shevchenko

WARNING: multiple messages have this Message-ID (diff)
From: andy.shevchenko@gmail.com (Andy Shevchenko)
To: linux-arm-kernel@lists.infradead.org
Subject: Synopsys Ethernet QoS Driver
Date: Wed, 7 Dec 2016 22:15:55 +0200	[thread overview]
Message-ID: <CAHp75Vf2ZncJcGguueh2fCsHaZVin8qGSk+hDUt+uRg8ffgZbQ@mail.gmail.com> (raw)
In-Reply-To: <87c8a24b-0812-7850-cb3f-7be691bab432@st.com>

On Mon, Nov 21, 2016 at 2:52 PM, Giuseppe CAVALLARO
<peppe.cavallaro@st.com> wrote:

First of all, +1 to (re-)use stmmac.

> The stmmac drivers run since many years on several platforms
> (sh4, stm32, arm, x86, mips ...) and it supports an huge of amount of
> configurations starting from 3.1x to 3.7x databooks.

As Intel employee who did some clean ups to that, acknowledge above.

> Concerning the stmicro/stmmac naming, these come from a really old
> story and have no issue to adopt new folder/file names.

I don't think it would be best idea for platform driver (though we can
keep driver's name in the structure in async with file name).

-- 
With Best Regards,
Andy Shevchenko

  parent reply	other threads:[~2016-12-07 20:32 UTC|newest]

Thread overview: 63+ 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 12:52           ` Giuseppe CAVALLARO
2016-11-21 12:52           ` Giuseppe CAVALLARO
2016-11-21 13:28           ` Lars Persson
2016-11-21 13:28             ` Lars Persson
2016-11-21 14:25             ` Giuseppe CAVALLARO
2016-11-21 14:25               ` Giuseppe CAVALLARO
2016-11-21 15:06               ` Joao Pinto
2016-11-21 15:06                 ` Joao Pinto
2016-11-21 15:43                 ` Lars Persson
2016-11-21 15:43                   ` Lars Persson
2016-11-21 16:11                   ` Joao Pinto
2016-11-21 16:11                     ` Joao Pinto
2016-11-22 14:16                     ` Joao Pinto
2016-11-22 14:16                       ` Joao Pinto
2016-11-23 10:59                       ` Giuseppe CAVALLARO
2016-11-23 10:59                         ` Giuseppe CAVALLARO
2016-11-23 10:59                         ` Giuseppe CAVALLARO
2016-11-23 11:10                         ` Joao Pinto
2016-11-23 11:10                           ` Joao Pinto
2016-11-23 11:41                           ` Lars Persson
2016-11-23 11:41                             ` Lars Persson
2016-11-23 11:43                             ` Joao Pinto
2016-11-23 11:43                               ` Joao Pinto
2016-11-25  8:55                               ` Giuseppe CAVALLARO
2016-11-25  8:55                                 ` Giuseppe CAVALLARO
2016-11-25  8:55                                 ` Giuseppe CAVALLARO
2016-12-07  9:41                       ` Pavel Machek
2016-12-07  9:41                         ` Pavel Machek
2016-11-21 13:48           ` Joao Pinto
2016-11-21 13:48             ` Joao Pinto
2016-11-21 13:48             ` Joao Pinto
2016-11-21 14:36             ` Giuseppe CAVALLARO
2016-11-21 14:36               ` Giuseppe CAVALLARO
2016-11-21 14:36               ` Giuseppe CAVALLARO
2016-11-21 15:00               ` Joao Pinto
2016-11-21 15:00                 ` Joao Pinto
2016-11-21 15:00                 ` Joao Pinto
2016-11-21 15:03                 ` Giuseppe CAVALLARO
2016-11-21 15:03                   ` Giuseppe CAVALLARO
2016-11-21 15:03                   ` Giuseppe CAVALLARO
2016-11-21 15:14                   ` Joao Pinto
2016-11-21 15:14                     ` Joao Pinto
2016-11-21 15:14                     ` Joao Pinto
2016-11-22  8:38               ` Ozgur Karatas
2016-11-22  8:38                 ` Ozgur Karatas
2016-11-23  8:02                 ` Giuseppe CAVALLARO
2016-11-23  8:02                   ` Giuseppe CAVALLARO
2016-11-23  8:02                   ` Giuseppe CAVALLARO
2016-12-07 20:15           ` Andy Shevchenko [this message]
2016-12-07 20:15             ` Andy Shevchenko
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=CAHp75Vf2ZncJcGguueh2fCsHaZVin8qGSk+hDUt+uRg8ffgZbQ@mail.gmail.com \
    --to=andy.shevchenko@gmail.com \
    --cc=CARLOS.PALMINHA@synopsys.com \
    --cc=Joao.Pinto@synopsys.com \
    --cc=alexandre.torgue@st.com \
    --cc=andreas.irestal@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 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.