Re: atl2 network driver status
From: Jay Cliburn
Date: Thu Oct 02 2008 - 19:36:28 EST
On Thu, 2 Oct 2008 18:29:43 -0500
Jay Cliburn <jcliburn@xxxxxxxxx> wrote:
> On Thu, 2 Oct 2008 16:21:48 -0700
> Greg KH <greg@xxxxxxxxx> wrote:
>
> > On Thu, Oct 02, 2008 at 06:17:31PM -0500, Jay Cliburn wrote:
> > > On Thu, 2 Oct 2008 16:02:46 -0700
> > > Greg KH <greg@xxxxxxxxx> 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?
> > >
> > > Hi Greg,
> > >
> > > It's in net-next-2.6.
> > >
> > > http://marc.info/?l=linux-netdev&m=122144021209242&w=2
> >
> > Nice, so that means it's going to be in 2.6.28?
>
> I think so. As I understand it, net-next-2.6 is Dave Miller's git
> tree for stuff destined for 2.6.28.
Yep, here it is: Dave's description of his two main trees.
So atl2 will be in 2.6.28.
Date: Sat, 19 Apr 2008 17:35:10 -0700 (PDT)
From: David Miller <davem@xxxxxxxxxxxxx>
To: sfr@xxxxxxxxxxxxxxxx
Cc: akpm@xxxxxxxxxxxxxxxxxxxx, netdev@xxxxxxxxxxxxxxx
Subject: New GIT net tree naming...
Based upon feedback from Andrew and others I'm now starting
to use a new naming scheme for my GIT trees:
For changes against Linus's current tree:
master.kernel.org:/pub/scm/linux/kernel/git/davem/net-2.6.git
For development meant to be merged in the next merge
window we have:
master.kernel.org:/pub/scm/linux/kernel/git/davem/net-next-2.6.git
Andrew/Stephen, let me know if this works for you. This way
the tree names will never change.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/