linux-kernel - Re: [PATCH 1/2] cciss: version update, new hw

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: <20060911153140.3f2433a9.akpm@osdl.org>
Date:	Mon, 11 Sep 2006 15:31:40 -0700
From:	Andrew Morton <akpm@...l.org>
To:	"Mike Miller (OS Dev)" <mikem@...rdog.cca.cpqcorp.net>
Cc:	axboe@...e.de, linux-kernel@...r.kernel.org,
	linux-scsi@...er.kernel.org
Subject: Re: [PATCH 1/2] cciss: version update, new hw

On Mon, 11 Sep 2006 16:31:26 -0500
"Mike Miller (OS Dev)" <mikem@...rdog.cca.cpqcorp.net> wrote:

> This patch adds support for new hardware and bumps the version to 3.6.10. It
> seems there were several changes introduced including soft_irq. I decided
> to bump the major number to reflect these changes. Since we're still 
> supporting older vendor kernels I need some way differenciate between kernel
> versions <=2.6.10 and newer kernels >=2.6.16. 
> I hate to send this in -rc6 but it seems like 2.6.18 is having a tough time
> getting out the gate. Please consider this for inclusion.

Adding a new device ID is a bit of a no-brainer - in fact bumping the
version number seems more risky than adding a device ID.

I'd be OK with a 2.6.18 merge, and shall send it into Linus unless Jens
nacks it, or gets there first.

-
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/