public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Len Brown <lenb@kernel.org>
Cc: stable@kernel.org, linux-acpi@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [stable] [PATCH 2.6.23..2.6.27.stable] ACPI: delete OSI(Linux) DMI dmesg spam
Date: Tue, 9 Dec 2008 09:39:14 -0800	[thread overview]
Message-ID: <20081209173914.GC32344@kroah.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0812081556060.4406@localhost.localdomain>

On Mon, Dec 08, 2008 at 04:03:07PM -0500, Len Brown wrote:
> Per 2.6.28 commit a6e0887f21bbab337ee32d9c0a84d7c0b6e9141b,
> stop soliciting DMI info for this BIOS issue.
> 
> Signed-off-by: Len Brown <len.brown@intel.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?

thanks,

greg k-h

> ---
> This patch applies cleanly to 2.6.26 and 2.6.27
> It applies with various offsets to 2.6.23, 2.6.24, 2.6.25
> 
> thanks,
> -Len Brown
> Intel Open Source Technology Center
> 
> diff --git a/drivers/acpi/osl.c b/drivers/acpi/osl.c
> index 235a138..b0d40aa 100644
> --- a/drivers/acpi/osl.c
> +++ b/drivers/acpi/osl.c
> @@ -1261,34 +1261,6 @@ acpi_status acpi_os_release_object(acpi_cache_t * cache, void *object)
>  	return (AE_OK);
>  }
>  
> -/**
> - *	acpi_dmi_dump - dump DMI slots needed for blacklist entry
> - *
> - *	Returns 0 on success
> - */
> -static int acpi_dmi_dump(void)
> -{
> -
> -	if (!dmi_available)
> -		return -1;
> -
> -	printk(KERN_NOTICE PREFIX "DMI System Vendor: %s\n",
> -		dmi_get_system_info(DMI_SYS_VENDOR));
> -	printk(KERN_NOTICE PREFIX "DMI Product Name: %s\n",
> -		dmi_get_system_info(DMI_PRODUCT_NAME));
> -	printk(KERN_NOTICE PREFIX "DMI Product Version: %s\n",
> -		dmi_get_system_info(DMI_PRODUCT_VERSION));
> -	printk(KERN_NOTICE PREFIX "DMI Board Name: %s\n",
> -		dmi_get_system_info(DMI_BOARD_NAME));
> -	printk(KERN_NOTICE PREFIX "DMI BIOS Vendor: %s\n",
> -		dmi_get_system_info(DMI_BIOS_VENDOR));
> -	printk(KERN_NOTICE PREFIX "DMI BIOS Date: %s\n",
> -		dmi_get_system_info(DMI_BIOS_DATE));
> -
> -	return 0;
> -}
> -
> -
>  /******************************************************************************
>   *
>   * FUNCTION:    acpi_os_validate_interface
> @@ -1315,14 +1287,6 @@ acpi_os_validate_interface (char *interface)
>  			osi_linux.cmdline ? " via cmdline" :
>  			osi_linux.dmi ? " via DMI" : "");
>  
> -		if (!osi_linux.dmi) {
> -			if (acpi_dmi_dump())
> -				printk(KERN_NOTICE PREFIX
> -					"[please extract dmidecode output]\n");
> -			printk(KERN_NOTICE PREFIX
> -				"Please send DMI info above to "
> -				"linux-acpi@vger.kernel.org\n");
> -		}
>  		if (!osi_linux.known && !osi_linux.cmdline) {
>  			printk(KERN_NOTICE PREFIX
>  				"If \"acpi_osi=%sLinux\" works better, "
> 
> _______________________________________________
> stable mailing list
> stable@linux.kernel.org
> http://linux.kernel.org/mailman/listinfo/stable

  reply	other threads:[~2008-12-09 17:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-08 21:03 [PATCH 2.6.23..2.6.27.stable] ACPI: delete OSI(Linux) DMI dmesg spam Len Brown
2008-12-09 17:39 ` Greg KH [this message]
2008-12-10  5:26   ` [stable] " Len Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081209173914.GC32344@kroah.com \
    --to=greg@kroah.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox