From: joe@perches.com (Joe Perches)
To: cocci@systeme.lip6.fr
Subject: [Cocci] printf vs. printk (was Re: Side-effect free printk?)
Date: Fri, 05 Dec 2014 07:26:49 -0800 [thread overview]
Message-ID: <1417793209.2721.53.camel@perches.com> (raw)
In-Reply-To: <1417793094.2721.51.camel@perches.com>
On Fri, 2014-12-05 at 07:24 -0800, Joe Perches wrote:
> My preference would be to eventually eliminate printk
> altogether but I don't see a real problem adding
> #define printf printk
> to include/linux/printk.h
>
> but
(bah, bad touchpad)
but I'm not going to write or ack that patch.
prev parent reply other threads:[~2014-12-05 15:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 17:50 [Cocci] Side-effect free printk? Joe Perches
2014-12-03 18:02 ` Julia Lawall
2014-12-03 18:05 ` Joe Perches
2014-12-05 10:32 ` [Cocci] printf vs. printk (was Re: Side-effect free printk?) Pavel Machek
2014-12-05 15:24 ` Joe Perches
2014-12-05 15:26 ` Joe Perches [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=1417793209.2721.53.camel@perches.com \
--to=joe@perches.com \
--cc=cocci@systeme.lip6.fr \
/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