netdev - Re: [GIT/PATCH v5] xen network backend driver

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: <20110314.132355.226777213.davem@davemloft.net>
Date:	Mon, 14 Mar 2011 13:23:55 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	Ian.Campbell@...citrix.com
Cc:	bhutchings@...arflare.com, netdev@...r.kernel.org,
	xen-devel@...ts.xensource.com, jeremy@...p.org,
	herbert@...dor.apana.org.au, konrad.wilk@...cle.com,
	romieu@...zoreil.com, shemminger@...tta.com, mirqus@...il.com
Subject: Re: [GIT/PATCH v5] xen network backend driver

From: Ian Campbell <Ian.Campbell@...citrix.com>
Date: Mon, 14 Mar 2011 19:30:40 +0000

> On Mon, 2011-03-14 at 18:40 +0000, Ben Hutchings wrote:
>> I know you have asked for this to be pulled, in order to retain its
>> history, but I'm not sure that David Miller will do this unless the
>> driver is at least buildable at each stage in the history.  (However,
>> given that the driver wouldn't be enabled before it's added, I'm not
>> sure it matters in this case.)
> 
> I think it should be, at least from the second commit onwards (modulo
> any mistakes made in the past).

I don't want to retain all of that history, there are so many broken
points in the history that the only thing you can do is go back and
add Kconfig commits to depend the driver upon BROKEN, and that in effect
changes the history devalueing it even further.

I just want one patch that adds the driver in it's most current state,
and that's all.

Thanks.
--
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