linux-kernel - Re: [PATCH] x86,idle: pr_debug information need separated

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]

Date:	Tue, 18 Dec 2012 22:46:31 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Youquan Song <youquan.song@...el.com>
Cc:	linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org,
	lenb@...nel.org, Youquan Song <youquan.song@...ux.intel.com>
Subject: Re: [PATCH] x86,idle: pr_debug information need separated

On Tuesday, December 18, 2012 12:26:02 PM Youquan Song wrote:
> When debug kernel, the the below information is found:
> intel_idle: unaware of model 0x1a MWAIT 4 please contact lenb@...nel.orgACPI: Device input0 -> No ACPI support
> 
> so this patch separates it.

Applied to linux-pm.git/linux-next as v3.8 material.

Thanks,
Rafael


> Signed-off-by: Youquan Song <youquan.song@...el.com>
> ---
>  drivers/idle/intel_idle.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/idle/intel_idle.c b/drivers/idle/intel_idle.c
> index b0f6b4c..eae6e3b 100644
> --- a/drivers/idle/intel_idle.c
> +++ b/drivers/idle/intel_idle.c
> @@ -518,7 +518,7 @@ static int intel_idle_cpuidle_driver_init(void)
>  			if (*cpuidle_state_table[cstate].name == '\0')
>  				pr_debug(PREFIX "unaware of model 0x%x"
>  					" MWAIT %d please"
> -					" contact lenb@...nel.org",
> +					" contact lenb@...nel.org\n",
>  				boot_cpu_data.x86_model, cstate);
>  			continue;
>  		}
> 
-- 
I speak only for myself.
Rafael J. Wysocki, 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/