public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: domen-CvScVCPLwOZg9hUCZPvPmw@public.gmane.org
To: len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	domen-CvScVCPLwOZg9hUCZPvPmw@public.gmane.org,
	clucas-FNWCkmgu6Xgh9ZMKESR00Q@public.gmane.org
Subject: [patch 2/2] printk: drivers/acpi/pci_link.c
Date: Fri, 08 Apr 2005 09:50:34 +0200	[thread overview]
Message-ID: <20050408075035.16A7C1EE91@trashy.coderock.org> (raw)



printk() calls should include appropriate KERN_* constant.

Signed-off-by: Christophe Lucas <clucas-FNWCkmgu6Xgh9ZMKESR00Q@public.gmane.org>
Signed-off-by: Domen Puncer <domen-CvScVCPLwOZg9hUCZPvPmw@public.gmane.org>
---


 kj-domen/drivers/acpi/pci_link.c |    2 +-
 1 files changed, 1 insertion(+), 1 deletion(-)

diff -puN drivers/acpi/pci_link.c~printk-drivers_acpi_pci_link drivers/acpi/pci_link.c
--- kj/drivers/acpi/pci_link.c~printk-drivers_acpi_pci_link	2005-04-05 12:57:57.000000000 +0200
+++ kj-domen/drivers/acpi/pci_link.c	2005-04-05 12:57:57.000000000 +0200
@@ -352,7 +352,7 @@ acpi_pci_link_set (
 		/* ignore resource_source, it's optional */
 		break;
 	default:
-		printk("ACPI BUG: resource_type %d\n", link->irq.resource_type);
+		printk(KERN_WARNING "ACPI BUG: resource_type %d\n", link->irq.resource_type);
 		result = -EINVAL;
 		goto end;
 
_


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

                 reply	other threads:[~2005-04-08  7:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20050408075035.16A7C1EE91@trashy.coderock.org \
    --to=domen-cvscvcplwozg9huczpvpmw@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=clucas-FNWCkmgu6Xgh9ZMKESR00Q@public.gmane.org \
    --cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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