public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Dave Jones <davej@redhat.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, gregkh@suse.de
Subject: Re: x86-64 mmconfig missing printk levels.
Date: Mon, 16 Oct 2006 12:38:37 +0200	[thread overview]
Message-ID: <200610161238.37282.ak@suse.de> (raw)
In-Reply-To: <20061011182105.GA1974@redhat.com>

On Wednesday 11 October 2006 20:21, Dave Jones wrote:
> Trivial bits..

Would be more for Greg.

-Andi

> 
> Signed-off-by: Dave Jones <davej@redhat.com>
> 
> --- local-git/arch/x86_64/pci/mmconfig.c~	2006-10-11 14:18:57.000000000 -0400
> +++ local-git/arch/x86_64/pci/mmconfig.c	2006-10-11 14:19:28.000000000 -0400
> @@ -220,7 +220,7 @@ void __init pci_mmcfg_init(int type)
>  
>  	pci_mmcfg_virt = kmalloc(sizeof(*pci_mmcfg_virt) * pci_mmcfg_config_num, GFP_KERNEL);
>  	if (pci_mmcfg_virt == NULL) {
> -		printk("PCI: Can not allocate memory for mmconfig structures\n");
> +		printk(KERN_ERR "PCI: Can not allocate memory for mmconfig structures\n");
>  		return;
>  	}
>  	for (i = 0; i < pci_mmcfg_config_num; ++i) {
> @@ -228,7 +228,7 @@ void __init pci_mmcfg_init(int type)
>  		pci_mmcfg_virt[i].virt = ioremap_nocache(pci_mmcfg_config[i].base_address,
>  							 MMCONFIG_APER_MAX);
>  		if (!pci_mmcfg_virt[i].virt) {
> -			printk("PCI: Cannot map mmconfig aperture for segment %d\n",
> +			printk(KERN_ERR "PCI: Cannot map mmconfig aperture for segment %d\n",
>  			       pci_mmcfg_config[i].pci_segment_group_number);
>  			return;
>  		}
> 

      reply	other threads:[~2006-10-16 10:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-11 18:21 x86-64 mmconfig missing printk levels Dave Jones
2006-10-16 10:38 ` Andi Kleen [this message]

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=200610161238.37282.ak@suse.de \
    --to=ak@suse.de \
    --cc=davej@redhat.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.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