From: Joe Perches <joe@perches.com>
To: kvm-ia64@vger.kernel.org
Subject: [PATCH 0/4] printk: cleanups of direct includes
Date: Wed, 25 May 2011 17:02:37 +0000 [thread overview]
Message-ID: <cover.1306342673.git.joe@perches.com> (raw)
printk.h is a subfile of kernel.h, do not allow it to
be included directly.
Joe Perches (4):
treewide: Remove direct includes of printk.h
staging: Remove direct includes of printk.h
printk: Don't allow direct inclusion
treewide: Remove asmlinkage from printk
arch/arm/kernel/early_printk.c | 2 +-
arch/ia64/kvm/vmm.c | 2 +-
arch/x86/kernel/early_printk.c | 2 +-
drivers/staging/brcm80211/brcmfmac/dhd_sdio.c | 1 -
drivers/staging/brcm80211/util/bcmutils.c | 1 -
drivers/staging/usbip/usbip_common.h | 2 +-
fs/ext4/inode.c | 1 -
include/linux/oprofile.h | 2 +-
include/linux/printk.h | 10 +++++++---
kernel/printk.c | 6 +++---
kernel/sysctl.c | 3 +--
11 files changed, 16 insertions(+), 16 deletions(-)
--
1.7.4.rc3
reply other threads:[~2011-05-25 17:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.1306342673.git.joe@perches.com \
--to=joe@perches.com \
--cc=kvm-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).