From: Paul Mundt <lethal@linux-sh.org>
To: Joe Perches <joe@perches.com>
Cc: Grant Likely <grant.likely@secretlab.ca>,
linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 7/8] irqdomain: trivial pr_fmt conversion.
Date: Sat, 19 May 2012 06:57:04 +0000 [thread overview]
Message-ID: <20120519065704.GB32537@linux-sh.org> (raw)
In-Reply-To: <1337409295.10521.4.camel@joe2Laptop>
On Fri, May 18, 2012 at 11:34:55PM -0700, Joe Perches wrote:
> On Sat, 2012-05-19 at 15:11 +0900, Paul Mundt wrote:
> > Convert to pr_fmt before things start to get out of hand and some
> > janitors start getting overly excited.
>
> ;) OK then, here's some trivia:
>
> > diff --git a/kernel/irq/irqdomain.c b/kernel/irq/irqdomain.c
> []
> > @@ -1,3 +1,5 @@
> > +#define pr_fmt(fmt) "irq: " fmt
>
> "irqdomain: " (KBUILD_MODNAME) may be more sensible
>
Perhaps. The point of the patch was to consolidate rather than change
behaviour. With a consolidation in place it's possible to change it to
whatever people are happy with.
> []
> > @@ -410,23 +412,23 @@ unsigned int irq_create_mapping(struct irq_domain *domain,
> > unsigned int hint;
> > int virq;
> >
> > - pr_debug("irq: irq_create_mapping(0x%p, 0x%lx)\n", domain, hwirq);
> > + pr_debug("irq_create_mapping(0x%p, 0x%lx)\n", domain, hwirq);
>
> "%s: ...", __func__, etc...
>
Unrelated to pr_fmt conversion. In any event, these debug calls are
unlikely to hang around for very long.
> > if (domain = NULL) {
> > - printk(KERN_WARNING "irq_create_mapping called for"
> > - " NULL domain, hwirq=%lx\n", hwirq);
> > + pr_warning("irq_create_mapping called for"
> > + " NULL domain, hwirq=%lx\n", hwirq);
>
> pr_warn("%s: called with NULL domain, hwirq=%lx\n", hwirq);
>
No. pr_warning() matches the log level, pr_warn() does not. A quick grep
also shoes more pr_warning() users than pr_warn(), so it sounds like you
have your work cut out for you. Good luck.
WARNING: multiple messages have this Message-ID (diff)
From: Paul Mundt <lethal@linux-sh.org>
To: Joe Perches <joe@perches.com>
Cc: Grant Likely <grant.likely@secretlab.ca>,
linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 7/8] irqdomain: trivial pr_fmt conversion.
Date: Sat, 19 May 2012 15:57:04 +0900 [thread overview]
Message-ID: <20120519065704.GB32537@linux-sh.org> (raw)
In-Reply-To: <1337409295.10521.4.camel@joe2Laptop>
On Fri, May 18, 2012 at 11:34:55PM -0700, Joe Perches wrote:
> On Sat, 2012-05-19 at 15:11 +0900, Paul Mundt wrote:
> > Convert to pr_fmt before things start to get out of hand and some
> > janitors start getting overly excited.
>
> ;) OK then, here's some trivia:
>
> > diff --git a/kernel/irq/irqdomain.c b/kernel/irq/irqdomain.c
> []
> > @@ -1,3 +1,5 @@
> > +#define pr_fmt(fmt) "irq: " fmt
>
> "irqdomain: " (KBUILD_MODNAME) may be more sensible
>
Perhaps. The point of the patch was to consolidate rather than change
behaviour. With a consolidation in place it's possible to change it to
whatever people are happy with.
> []
> > @@ -410,23 +412,23 @@ unsigned int irq_create_mapping(struct irq_domain *domain,
> > unsigned int hint;
> > int virq;
> >
> > - pr_debug("irq: irq_create_mapping(0x%p, 0x%lx)\n", domain, hwirq);
> > + pr_debug("irq_create_mapping(0x%p, 0x%lx)\n", domain, hwirq);
>
> "%s: ...", __func__, etc...
>
Unrelated to pr_fmt conversion. In any event, these debug calls are
unlikely to hang around for very long.
> > if (domain == NULL) {
> > - printk(KERN_WARNING "irq_create_mapping called for"
> > - " NULL domain, hwirq=%lx\n", hwirq);
> > + pr_warning("irq_create_mapping called for"
> > + " NULL domain, hwirq=%lx\n", hwirq);
>
> pr_warn("%s: called with NULL domain, hwirq=%lx\n", hwirq);
>
No. pr_warning() matches the log level, pr_warn() does not. A quick grep
also shoes more pr_warning() users than pr_warn(), so it sounds like you
have your work cut out for you. Good luck.
next prev parent reply other threads:[~2012-05-19 6:57 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-19 6:11 [PATCH 0/8] irqdomain cleanups + identity mapping support Paul Mundt
2012-05-19 6:11 ` Paul Mundt
2012-05-19 6:11 ` [PATCH 1/8] irqdomain: Support removal of IRQ domains Paul Mundt
2012-05-19 6:11 ` Paul Mundt
2012-05-19 18:34 ` Grant Likely
2012-05-19 18:34 ` Grant Likely
2012-05-19 6:11 ` [PATCH 2/8] irqdomain: Export remaining public API symbols Paul Mundt
2012-05-19 6:11 ` Paul Mundt
2012-05-19 18:34 ` Grant Likely
2012-05-19 18:34 ` Grant Likely
2012-05-19 6:11 ` [PATCH 3/8] irqdomain: Make irq_domain_simple_map() static Paul Mundt
2012-05-19 6:11 ` Paul Mundt
2012-05-19 18:35 ` Grant Likely
2012-05-19 18:35 ` Grant Likely
2012-05-19 6:11 ` [PATCH 4/8] irqdomain: Simple NUMA awareness Paul Mundt
2012-05-19 6:11 ` Paul Mundt
2012-05-19 18:41 ` Grant Likely
2012-05-19 18:41 ` Grant Likely
2012-05-21 4:46 ` Paul Mundt
2012-05-21 4:46 ` Paul Mundt
2012-05-19 6:11 ` [PATCH 5/8] irqdomain: Kill off duplicate definitions Paul Mundt
2012-05-19 6:11 ` Paul Mundt
2012-05-19 18:42 ` Grant Likely
2012-05-19 18:42 ` Grant Likely
2012-05-19 6:11 ` [PATCH 6/8] irqdomain: Support identity mapped VIRQ allocation Paul Mundt
2012-05-19 6:11 ` Paul Mundt
2012-05-19 20:21 ` Grant Likely
2012-05-19 20:21 ` Grant Likely
2012-05-21 4:55 ` Paul Mundt
2012-05-21 4:55 ` Paul Mundt
2012-05-19 6:11 ` [PATCH 7/8] irqdomain: trivial pr_fmt conversion Paul Mundt
2012-05-19 6:11 ` Paul Mundt
2012-05-19 6:34 ` Joe Perches
2012-05-19 6:34 ` Joe Perches
2012-05-19 6:57 ` Paul Mundt [this message]
2012-05-19 6:57 ` Paul Mundt
2012-05-19 18:49 ` Grant Likely
2012-05-19 18:49 ` Grant Likely
2012-05-19 6:11 ` [PATCH 8/8] irqdomain: Support insertion of existing IRQ allocations Paul Mundt
2012-05-19 6:11 ` Paul Mundt
2012-05-19 18:32 ` [PATCH 0/8] irqdomain cleanups + identity mapping support Grant Likely
2012-05-19 18:32 ` Grant Likely
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=20120519065704.GB32537@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=grant.likely@secretlab.ca \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.