netdev - Re: [PATCH 00/39] merge request for WiMAX kernel stack and i2400m 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: <20081125.134352.27718659.davem@davemloft.net>
Date:	Tue, 25 Nov 2008 13:43:52 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	inaky@...ux.intel.com
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH 00/39] merge request for WiMAX kernel stack and i2400m
 driver

From: Inaky Perez-Gonzalez <inaky@...ux.intel.com>
Date: Tue, 25 Nov 2008 08:57:10 -0800

> On Tuesday 25 November 2008, David Miller wrote:
> > From: Inaky Perez-Gonzalez <inaky@...ux.intel.com>
> > Date: Mon, 24 Nov 2008 13:50:23 -0800
> >
> > > This patchset (or the linux-wimax GIT tree at git.kernel.org) merges
> > > the WiMAX subsystem and driver for the Intel 2400m Wireless WiMAX
> > > connection to the tree. We'd like to get it in for the 2.6.29 merge
> > > window.
> >
> > You've made this difficult by creating the dependency on
> > the USB changes.
> >
> > So I can't, for example, merge this into the networking tree.
> > Is there some way you can make the driver work without the
> > USB changes even with some hack?
> 
> I know, but there was little choice. The error paths for device 
> recovery depend on those changes. That's why I suggest posting 
> through gregkh's tree once you guys give your approval. Then after
> it goes into the first merge window and it permeates to your tree,
> I'll rebase the linux-wimax tree to have you as upstream.

Ok, maybe that's what we'll have to do.
--
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