netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Mickey Rachamim <mickeyr@marvell.com>
Cc: "David S . Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"Vadym Kochan [C]" <vkochan@marvell.com>,
	"Taras Chornyi [C]" <tchornyi@marvell.com>
Subject: Re: [EXT] Re: [PATCH v2] MAINTAINERS: Add entry for Marvell Prestera Ethernet Switch driver
Date: Wed, 9 Dec 2020 23:34:01 +0100	[thread overview]
Message-ID: <20201209223401.GB2649111@lunn.ch> (raw)
In-Reply-To: <BN6PR18MB15873CD07E1B6BB1B6C21DE8BACC0@BN6PR18MB1587.namprd18.prod.outlook.com>

On Wed, Dec 09, 2020 at 09:38:52PM +0000, Mickey Rachamim wrote:
> Hi Andrew, 
> 
> > > You can see that only yesterday (Dec 8th) we had the first official 
> > > merge on this repo - this is the reason for the lack of commits.
> > > Marvell Switching group took strategic decision to open some aspects 
> > > of the Prestera family devices with the Open Source community and this 
> > > is the first step.
> > 
> > > As you realized - it will be used as a queue for all the features 
> > > targeted to be upstreamed.  New features are expected to be sent to 
> > > net-next very soon. (Like ACL/LAG/LLDP etc...)
> > 
> > Hi Mickey
> > 
> > I would actually expect this repo to hold a linux tree, probably based on net-next, and with a number of patches on top adding Prestera features, one by one.

Hi Mickey

Please get your mailer fixed. It seems to be re-wrapping other peoples
text, which is bad.

> A Buildroot based repo that includes specific platform patches will became public in the upcoming days. (As part of Marvell-Switching GitHub)

And please wrap your own text at around 65 characters. Standard
Netique RFC 1855 stuff.

> > 
> > Given your current structure, i don't see a direct path for this code into mainline.
> > 
> 
> Assuming the discussion is still on the 'W:' line;

Nope. I'm still talking about this repo of driver code. It is one
commit. Meaning you cannot do

git-format patch
git send-email --to=jakub --to=davem --cc=netdev *.patch

So you are basically going to have to re-write the code into a set of
patches. Which makes this repo pointless, in terms of kernel
development work. And that is what MAINTAINERS is all about.

	 Andrew

      reply	other threads:[~2020-12-09 22:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-05 16:43 [PATCH v2] MAINTAINERS: Add entry for Marvell Prestera Ethernet Switch driver Mickey Rachamim
2020-12-08  0:15 ` Jakub Kicinski
2020-12-08  9:22   ` [EXT] " Mickey Rachamim
2020-12-08 16:39     ` Jakub Kicinski
2020-12-08 18:57       ` Jakub Kicinski
2020-12-09 13:22         ` Mickey Rachamim
2020-12-09 16:24           ` Andrew Lunn
2020-12-09 21:38             ` Mickey Rachamim
2020-12-09 22:34               ` Andrew Lunn [this message]

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=20201209223401.GB2649111@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=mickeyr@marvell.com \
    --cc=netdev@vger.kernel.org \
    --cc=tchornyi@marvell.com \
    --cc=vkochan@marvell.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).