lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Wed, 9 Dec 2020 23:34:01 +0100
From:   Andrew Lunn <andrew@...n.ch>
To:     Mickey Rachamim <mickeyr@...vell.com>
Cc:     "David S . Miller" <davem@...emloft.net>,
        Jakub Kicinski <kuba@...nel.org>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "Vadym Kochan [C]" <vkochan@...vell.com>,
        "Taras Chornyi [C]" <tchornyi@...vell.com>
Subject: Re: [EXT] Re: [PATCH v2] MAINTAINERS: Add entry for Marvell Prestera
 Ethernet Switch driver

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

Powered by blists - more mailing lists