public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Glauber Costa <gcosta@redhat.com>
To: Len Brown <lenb@kernel.org>
Cc: akpm@linux-foundation.org, linux-acpi@vger.kernel.org,
	"Thomas Renninger (Novell/SUSE)" <trenn@suse.de>,
	mm-commits@vger.kernel.org
Subject: Re: + acpi-use-acpi_debug_print-instead-of-printk.patch added to -mm tree
Date: Fri, 15 Feb 2008 21:21:52 -0200	[thread overview]
Message-ID: <47B61E90.6070005@redhat.com> (raw)
In-Reply-To: <200802151712.36300.lenb@kernel.org>

Len Brown wrote:
> I.e. this printk will be present in a production shipping distro kernel
> even if you move to to ACPI_DEBUG_PRINT from printk.
Yes, but you can still disable it. And if you do, all the messages will 
vanish, but this will stay.

> The only variable  is the default verbosity level.
> 
> Thomas, what verbosity level do you use?
in this patch, I used the same verbosity level as the EJECT request. So
if it is not okay for SuSe, I suggest changing all the others too.

> thanks,
> -Len
> 
> On Friday 15 February 2008 16:28, akpm@linux-foundation.org wrote:
>> The patch titled
>>      acpi: use ACPI_DEBUG_PRINT instead of printk
>> has been added to the -mm tree.  Its filename is
>>      acpi-use-acpi_debug_print-instead-of-printk.patch
>>
>> Before you just go and hit "reply", please:
>>    a) Consider who else should be cc'ed
>>    b) Prefer to cc a suitable mailing list as well
>>    c) Ideally: find the original patch on the mailing list and do a
>>       reply-to-all to that, adding suitable additional cc's
>>
>> *** Remember to use Documentation/SubmitChecklist when testing your code ***
>>
>> See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
>> out what to do about this
>>
>> The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
>>
>> ------------------------------------------------------
>> Subject: acpi: use ACPI_DEBUG_PRINT instead of printk
>> From: Glauber Costa <gcosta@redhat.com>
>>
>> For consistency, use ACPI_DEBUG_PRINT instead of printk in
>> acpi_processor_hotplug_notify() for BUS_CHECK and DEVICE_CHECK events
>>
>> Signed-off-by: Glauber Costa <gcosta@redhat.com>
>> Cc: Len Brown <lenb@kernel.org>
>> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
>> ---
>>
>>  drivers/acpi/processor_core.c |    5 +++--
>>  1 file changed, 3 insertions(+), 2 deletions(-)
>>
>> diff -puN drivers/acpi/processor_core.c~acpi-use-acpi_debug_print-instead-of-printk drivers/acpi/processor_core.c
>> --- a/drivers/acpi/processor_core.c~acpi-use-acpi_debug_print-instead-of-printk
>> +++ a/drivers/acpi/processor_core.c
>> @@ -890,9 +890,10 @@ acpi_processor_hotplug_notify(acpi_handl
>>  	switch (event) {
>>  	case ACPI_NOTIFY_BUS_CHECK:
>>  	case ACPI_NOTIFY_DEVICE_CHECK:
>> -		printk("Processor driver received %s event\n",
>> +		ACPI_DEBUG_PRINT((ACPI_DB_INFO,
>> +		"Processor driver received %s event\n",
>>  		       (event == ACPI_NOTIFY_BUS_CHECK) ?
>> -		       "ACPI_NOTIFY_BUS_CHECK" : "ACPI_NOTIFY_DEVICE_CHECK");
>> +		       "ACPI_NOTIFY_BUS_CHECK" : "ACPI_NOTIFY_DEVICE_CHECK"));
>>  
>>  		if (!is_processor_present(handle))
>>  			break;
>> _
>>
>> Patches currently in -mm which might be from gcosta@redhat.com are
>>
>> remove-is_processor_present-prototype.patch
>> acpi-use-acpi_debug_print-instead-of-printk.patch
>> git-kvm.patch
>>


  reply	other threads:[~2008-02-15 23:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200802152128.m1FLSMGi024897@imap1.linux-foundation.org>
2008-02-15 22:12 ` + acpi-use-acpi_debug_print-instead-of-printk.patch added to -mm tree Len Brown
2008-02-15 23:21   ` Glauber Costa [this message]
2008-02-16 23:33     ` Thomas Renninger

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=47B61E90.6070005@redhat.com \
    --to=gcosta@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=trenn@suse.de \
    /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