linux-kernel - Re: atl2 network driver status

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: <20081002230603.GA11609@kroah.com>
Date:	Thu, 2 Oct 2008 16:06:03 -0700
From:	Greg KH <greg@...ah.com>
To:	xiong.huang@...eros.com, csnook@...hat.com
Cc:	netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: atl2 network driver status

On Thu, Oct 02, 2008 at 04:02:46PM -0700, Greg KH wrote:
> Hi,
> 
> In looking for drivers to add to drivers/staging/ I ran across the atl2
> driver that is currently in the Fedora and Ubuntu kernel trees.
> 
> This driver doesn't look to be scheduled for inclusion in the upstream
> netdev git tree for submission for 2.6.28, is there any reason why it is
> still out-of-the-tree?
> 
> And, if it's not going into 2.6.28, any objection for me adding it to
> the drivers/staging/ tree?  If so, I need a list of reasons why it is
> not merged upstream properly so far so that people know what to work on
> in order to get it there.

Ok, in looking at the code, I see a list of things that probably need to
be fixed up properly, but it would be nice to see what others think the
reasons are :)

thanks,

greg k-h
--
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/