linux-kernel - Re: [patch] x86, serial: always probe for legacy COM ports

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: <46AA53E3.5080501@garzik.org>
Date:	Fri, 27 Jul 2007 16:21:55 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Bjorn Helgaas <bjorn.helgaas@...com>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	Russell King <rmk@....linux.org.uk>,
	Adam Belay <ambx1@....rr.com>, Len Brown <lenb@...nel.org>,
	Matthew Garrett <mjg59@...f.ucam.org>,
	Sébastien Dugué <sebastien.dugue@...l.net>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [patch] x86, serial: always probe for legacy COM ports

Bjorn Helgaas wrote:
> On Friday 27 July 2007 12:05:51 pm Jeff Garzik wrote:
>> This is still incomplete, as repeatedly stated.  Here is the email, again.

> OK, uncle!  I'll work on your helpful advice (thanks for that), but
> it feels too risky for this stage of 2.6.23.  Maybe I can come up with
> something for a future release.

The changeset in the kernel is too risky _without_ the changes I described.

Hence the repeated use of the word "incomplete."

* The patch has transition issues, when you shuffle users from one 
device driver to another.  Existing change should not be deployed 
without ensuring breakage is unlikely.

* The new driver is missing module unload support.  Existing change 
should not be deployed without this.

* DOCUMENT the user visible changes.  Existing change should not be 
deployed without this.

	Jeff



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