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: <20070523002534.GB3390@sequoia.sous-sol.org>
Date:	Tue, 22 May 2007 17:25:34 -0700
From:	Chris Wright <chrisw@...s-sol.org>
To:	Jeff Garzik <jeff@...zik.org>
Cc:	Chris Wright <chrisw@...s-sol.org>, Greg KH <greg@...ah.com>,
	Chuck Ebbert <cebbert@...hat.com>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [stable] Wanted: Allow adding new device IDs during the
	-stable cycle

* Jeff Garzik (jeff@...zik.org) wrote:
> Chris Wright wrote:
> >2) In theory new hardware can seem to work with a simple PCI ID
> >update, and later we find it needs extra quirk handling or specific
> >driver support.  This could mean adding buggy support for new hardware
> >to -stable.  In practice, hopefully this isn't a real issue.
> 
> No need to worry about theory.  Since you are (or should be???) taking 
> stuff solely from upstream, you should already know what is needed, or not.

Yup, it's definitely handwavy.  If it's a problem we can address it then.

thanks,
-chris
-
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