From: Joe Perches <joe@perches.com>
To: linux-kernel@vger.kernel.org
Cc: Rusty Russell <rusty@rustcorp.com.au>
Subject: [PATCH 0/2] kernel/module.c: A little neatening
Date: Sat, 30 Oct 2010 16:58:20 -0700 [thread overview]
Message-ID: <cover.1288482645.git.joe@perches.com> (raw)
Joe Perches (2):
kernel/module.c: Use pr_<level> and pr_fmt
kernel/module.c: Use pr_debug and other neatening
kernel/module.c | 305 ++++++++++++++++++++++++++-----------------------------
1 files changed, 146 insertions(+), 159 deletions(-)
--
1.7.3.1.g432b3.dirty
next reply other threads:[~2010-10-30 23:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-30 23:58 Joe Perches [this message]
2010-10-30 23:58 ` [PATCH 1/2] kernel/module.c: Use pr_<level> and pr_fmt Joe Perches
2010-10-31 4:04 ` Arnaud Lacombe
2010-10-31 4:20 ` Joe Perches
2010-10-30 23:58 ` [PATCH 2/2] kernel/module.c: Use pr_debug and other neatening Joe Perches
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=cover.1288482645.git.joe@perches.com \
--to=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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.