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] [day] [month] [year] [list]
Message-Id: <20071217124408.284886a6.akpm@linux-foundation.org>
Date:	Mon, 17 Dec 2007 12:44:08 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Jiri Kosina <jkosina@...e.cz>
Cc:	dsterba@...e.cz, linux-kernel@...r.kernel.org,
	linux-pcmcia@...ts.infradead.org
Subject: Re: [PATCH V2] ipwireless_cs driver for 4G PC Card

On Mon, 17 Dec 2007 13:58:09 +0100 (CET)
Jiri Kosina <jkosina@...e.cz> wrote:

> On Mon, 17 Dec 2007, Andrew Morton wrote:
> 
> > > Andrew, what is your position on merging this into your 2.6.25 queue 
> > > please? David has fixed all the issues that came up during review, so 
> > > it seems to be that it's time for the driver to be merged during the 
> > > upcoming merge window. If you take it, I am perfectly fine with you 
> > > dropping the ipwireless_cs git tree from -mm lineup.
> > I'd have thought that you'd merge it into git-ipwireless_cs.patch and that
> > you would then take care of merging it into mainline at an appropriate
> > time?
> 
> I'd normally send this through PCMCIA maintainer's tree, but as long as 
> there is no such thing, I thought that merging through you is the best 
> thing to do. I don't want to bother Linus with pull request for a single 
> new driver.
> 

Linus will cope ;)

Assuming that you've reviewed the driver and have some understanding of
what it does and how it does it, you're way ahead of me.  Please go ahead
and merge it when you think that is appropriate.  
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ