From: Prarit Bhargava <prarit@redhat.com>
To: Prarit Bhargava <prarit@redhat.com>
Cc: yinghai@kernel.org, akpm@linux-foundation.org, mingo@elte.hu,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH]: REPOST cleanup debug message in init_kstat_irqs()
Date: Tue, 06 Apr 2010 09:48:33 -0400 [thread overview]
Message-ID: <4BBB3BB1.4070501@redhat.com> (raw)
In-Reply-To: <20100406134001.22289.47490.sendpatchset@prarit.bos.redhat.com>
Whoops... Subject should have been REPOST cleanup debug message in
irq_to_desc_alloc_node()
Sorry 'bout that.
P.
Prarit Bhargava wrote:
> [Sending to a wider audience this time, cc'ing Andrew and Ingo directly]
>
> Clean up debug messages in irq_to_desc_alloc_node().
>
> This debug message can result in valid output like
>
> alloc irq_desc for 73 on node -1
>
> which looks like alot like an error message.
>
> This debug statement has been in the kernel for about a year, so I think it is
> safe to remove it and report the irq and node in the error case instead.
>
> Signed-off-by: Prarit Bhargava <prarit@redhat.com>
>
> diff --git a/kernel/irq/handle.c b/kernel/irq/handle.c
> index 17c71bb..5c3e38e 100644
> --- a/kernel/irq/handle.c
> +++ b/kernel/irq/handle.c
> @@ -224,9 +224,10 @@ struct irq_desc * __ref irq_to_desc_alloc_node(unsigned int irq, int node)
> else
> desc = alloc_bootmem_node(NODE_DATA(node), sizeof(*desc));
>
> - printk(KERN_DEBUG " alloc irq_desc for %d on node %d\n", irq, node);
> if (!desc) {
> - printk(KERN_ERR "can not alloc irq_desc\n");
> + printk(KERN_ERR
> + "can not alloc irq_desc for irq %d on node %d\n",
> + irq, node);
> BUG_ON(1);
> }
> init_one_irq_desc(irq, desc, node);
>
parent reply other threads:[~2010-04-06 13:49 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20100406134001.22289.47490.sendpatchset@prarit.bos.redhat.com>]
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=4BBB3BB1.4070501@redhat.com \
--to=prarit@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=yinghai@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