netdev - Re: [GIT PULL] Please Pull Mellanox Shared Code

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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <e88d3000-f137-181e-4ea2-cd33101dd57c@redhat.com>
Date:	Tue, 14 Jun 2016 13:16:50 -0400
From:	Doug Ledford <dledford@...hat.com>
To:	David Miller <davem@...emloft.net>, leon@...nel.org
Cc:	linux-rdma@...r.kernel.org, netdev@...r.kernel.org,
	matanb@...lanox.com, saeedm@...lanox.com
Subject: Re: [GIT PULL] Please Pull Mellanox Shared Code

On 6/14/2016 3:02 AM, David Miller wrote:
> 
> Please, just stop right now.
> 
> We're not asking for the a huge patch covering the entire pull
> request.
> 
> We're asking for you to post a patch series, one per commit, and as
> numbered, fresh, new mailing list patch postings.  As if you were
> submitting these changes for the very first time to the list.
> 
> Please ask a colleague for how to do this properly before you spam the
> list again with more unnecessary and improperly formatted submissions.

Dave,

He's doing what Linus requested from Mellanox.  They were instructed to
identify all of the coming changes in the next release where patches
sent through your tree and patches sent through my tree would have
conflicts.  They were then instructed to make git commits that merged
those changes and have both you and I pull them (please note "pull", not
git am patches) so that we have the exact same commit hashes in our
trees and git will do the right thing when your tree and my tree are
merged in the next merge window.  As it turns out the conflicts are
mainly in this firmware offset definition file.  They just put all of
the needed changes in there in one commit.  I doubt they have individual
patches here.  This was a custom made patch who's sole purpose is to
combine all the otherwise possibly conflicting changes in one place.
I'm sure they could split it out into different commits, but they
wouldn't be full commits, just the portion that applies to this firmware
file.

--
Doug Ledford <dledford@...hat.com>
	GPG Key ID: 0E572FDD

Download attachment "signature.asc" of type "application/pgp-signature" (885 bytes)