From: Joe Perches <joe@perches.com>
To: linux-parisc@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-usb@vger.kernel.org
Cc: linux-alpha@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
microblaze-uclinux@itee.uq.edu.au, linuxppc-dev@lists.ozlabs.org,
sparclinux@vger.kernel.org, devel@driverdev.osuosl.org
Subject: [PATCH trivial next 0/9] treewide: Use vsprintf extention %pf
Date: Tue, 28 Feb 2012 10:49:29 -0800 [thread overview]
Message-ID: <cover.1330454853.git.joe@perches.com> (raw)
Emit the actual function name when possible
Joe Perches (9):
sparc: Use vsprintf extention %pf with builtin_return_address
alpha: Use vsprintf extention %pf with builtin_return_address
arm: Use vsprintf extention %pf with builtin_return_address
microblaze: Use vsprintf extention %pf with builtin_return_address
powerpc: Use vsprintf extention %pf with builtin_return_address
parisc: Use vsprintf extention %pf with builtin_return_address
scsi: Use vsprintf extention %pf with builtin_return_address
staging: ramster: Use vsprintf extention %pf with builtin_return_address
gadget: Use vsprintf extention %pf with builtin_return_address
arch/alpha/kernel/pci_iommu.c | 20 ++++++++++----------
arch/arm/nwfpe/fpmodule.c | 2 +-
arch/microblaze/mm/pgtable.c | 2 +-
arch/powerpc/mm/pgtable_32.c | 2 +-
arch/sparc/kernel/ds.c | 2 +-
arch/sparc/mm/srmmu.c | 2 +-
drivers/parisc/superio.c | 2 +-
drivers/scsi/esp_scsi.c | 2 +-
drivers/staging/ramster/cluster/heartbeat.c | 4 ++--
drivers/usb/gadget/u_serial.c | 2 +-
10 files changed, 20 insertions(+), 20 deletions(-)
--
1.7.8.111.gad25c.dirty
next reply other threads:[~2012-02-28 18:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 18:49 Joe Perches [this message]
2012-02-28 18:49 ` [PATCH trivial next 2/9] alpha: Use vsprintf extention %pf with builtin_return_address 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.1330454853.git.joe@perches.com \
--to=joe@perches.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=microblaze-uclinux@itee.uq.edu.au \
--cc=sparclinux@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 NNTP newsgroup(s).