netdev - Re: [PATCH 00/45] Update bna driver version to 3.0.2.0

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20110718.185805.413849001475627611.davem@davemloft.net>
Date:	Mon, 18 Jul 2011 18:58:05 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	rmody@...cade.com
Cc:	netdev@...r.kernel.org, adapter_linux_open_src_team@...cade.com
Subject: Re: [PATCH 00/45] Update bna driver version to 3.0.2.0

From: Rasesh Mody <rmody@...cade.com>
Date: Mon, 18 Jul 2011 17:48:03 -0700

> We wanted to avoid submitting developing code that could break
> upstream driver due to partial changes.

So what you're saying is that if only some of the patches are applied
the driver will not work properly?

That's not allowed either, your set of changes must be fully
bisectable meaning that at any point in the series the driver
must still compile and work properly.

You guys need to sort out how you guys submit your changes.

When you have 4 patches ready to go, post them immediately.

Because if there are fundamental problem with the first 4,
everything else that depends upon them will need to change.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html