linux-kernel - Re: git repository for SR-IOV development?

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]

Date:	Thu, 6 Nov 2008 11:58:25 -0800 (PST)
From:	H L <swdevyid@...oo.com>
To:	Greg KH <greg@...ah.com>
Cc:	Yu Zhao <yu.zhao@...el.com>, randy.dunlap@...cle.com,
	grundler@...isc-linux.org, achiang@...com, matthew@....cx,
	linux-pci@...r.kernel.org, rdreier@...co.com,
	linux-kernel@...r.kernel.org, jbarnes@...tuousgeek.org,
	virtualization@...ts.linux-foundation.org, kvm@...r.kernel.org,
	mingo@...e.hu, Xen-devel List <xen-devel@...ts.xensource.com>
Subject: Re: git repository for SR-IOV development?

--- On Thu, 11/6/08, Greg KH <greg@...ah.com> wrote:

> On Thu, Nov 06, 2008 at 08:51:09AM -0800, H L wrote:
> > 
> > Has anyone initiated or given consideration to the
> creation of a git
> > repository (say, on kernel.org) for SR-IOV
> development?
> 
> Why?  It's only a few patches, right?  Why would it
> need a whole new git
> tree?

So as to minimize the time and effort patching a kernel, especially if the tree (and/or hash level) against which the patches were created fails to be specified on a mailing-list.  Plus, there appears to be questions raised on how, precisely, the implementation should ultimately be modeled and especially given that, who knows at this point what number of patches will ultimately be submitted?  I know I've built the "7-patch" one (painfully, by the way), and I'm aware there's another 15-patch set out there which I've not yet examined.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/