From: Johannes Weiner <hannes@saeurebad.de>
To: "Mike Frysinger" <vapier.adi@gmail.com>
Cc: "Alan Cox" <alan@lxorguk.ukuu.org.uk>,
"Marc Pignat" <marc.pignat@hevs.ch>,
wim@iguana.be, linux-kernel@vger.kernel.org
Subject: printk-wrapper with sectionized string constants [was: Re: [RFC, PATCH] watchdog on gpio]
Date: Mon, 14 Jan 2008 14:56:52 +0100 [thread overview]
Message-ID: <87prw4jysb.fsf_-_@saeurebad.de> (raw)
In-Reply-To: <8bd0f97a0801140503t484ab61clcf41f4e4ea913fe4@mail.gmail.com> (Mike Frysinger's message of "Mon, 14 Jan 2008 08:03:29 -0500")
Hi,
"Mike Frysinger" <vapier.adi@gmail.com> writes:
>> How about:
>>
>> #define init_printk(fmt, args...) ({ \
>> static const __init char __fmt[] = fmt; \
>> printk(__fmt, args); \
>> })
>>
>> Now it returns the printk result.
>
> i wasnt really worried about that ... i was worried about other random
> things i may have missed
Ok.
> your dropping of ## wont work as you need gcc to expand args and take
> away the , in the simple 1 arg case:
> init_printk("MOO");
Whoops, totally oversaw this one. Of course, this must be in.
Perhaps an even more generic solution would be good, like this:
#define section_printk(sect, fmt, args...) ({ \
static const sect char __fmt[] = fmt; \
printk(__fmt, ## args); \
})
And then just have convenience wrappers like {,dev}init_printk, ... etc.
Can someone please shout at us if there is a fundamental problem with
this approach?
Hannes
prev parent reply other threads:[~2008-01-14 13:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 15:11 [RFC, PATCH] watchdog on gpio Marc Pignat
2008-01-10 17:14 ` Ben Dooks
2008-01-11 16:40 ` Florian Fainelli
2008-01-14 7:34 ` Marc Pignat
2008-01-14 8:08 ` Mike Frysinger
2008-01-14 8:04 ` Mike Frysinger
2008-01-14 9:03 ` Alan Cox
2008-01-14 9:28 ` Mike Frysinger
2008-01-14 9:29 ` Alan Cox
2008-01-14 9:45 ` Mike Frysinger
2008-01-14 12:14 ` Haavard Skinnemoen
2008-01-14 12:22 ` Mike Frysinger
2008-01-14 13:30 ` Haavard Skinnemoen
2008-01-14 12:49 ` Johannes Weiner
2008-01-14 13:03 ` Mike Frysinger
2008-01-14 13:56 ` Johannes Weiner [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=87prw4jysb.fsf_-_@saeurebad.de \
--to=hannes@saeurebad.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.pignat@hevs.ch \
--cc=vapier.adi@gmail.com \
--cc=wim@iguana.be \
/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.