linux-kernel - Re: [stable] [PATCH 2.6.23..2.6.27.stable] ACPI: delete OSI(Linux) DMI dmesg spam

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: <alpine.LFD.2.00.0812100023150.17146@localhost.localdomain>
Date:	Wed, 10 Dec 2008 00:26:48 -0500 (EST)
From:	Len Brown <lenb@...nel.org>
To:	Greg KH <greg@...ah.com>
Cc:	stable@...nel.org, linux-acpi@...r.kernel.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [stable] [PATCH 2.6.23..2.6.27.stable] ACPI: delete OSI(Linux) DMI
 dmesg spam


> > Per 2.6.28 commit a6e0887f21bbab337ee32d9c0a84d7c0b6e9141b,
> > stop soliciting DMI info for this BIOS issue.
> > 
> > Signed-off-by: Len Brown <len.brown@...el.com>
> 
> I don't understand, this isn't commit a6e0887f21bb upstream, right?
> 
> Is this patch upstream?  Or is it just that you don't want to get these
> messages anymore because it is fixed in 2.6.28 now?

We could port the upstream patch to the old .stable releases,
but I though it would cause less conflicts to instead
apply this simpler version that doesn't touch the DMI lists.

The reason we're turning off this message is because
at this point we don't think we'll learn anything new from additional
user feedback.

thanks,
-Len Brown
Intel Open Source Technology Center
--
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/