From: Joe Perches <joe@perches.com>
To: linux-kernel@vger.kernel.org
Cc: Paul Mackerras <paulus@samba.org>, linuxppc-dev@lists.ozlabs.org
Subject: [PATCH 0/2] powerpc: pci-ioda: Neatening
Date: Sun, 21 Sep 2014 10:55:04 -0700 [thread overview]
Message-ID: <cover.1411320262.git.joe@perches.com> (raw)
printk calls should return void
Joe Perches (2):
powerpc: pci-ioda: Remove unnecessary return value from printk
powerpc: pci-ioda: Use a single function to emit logging messages
(compiled/untested)
arch/powerpc/platforms/powernv/pci-ioda.c | 61 +++++++++++++++----------------
1 file changed, 30 insertions(+), 31 deletions(-)
--
1.8.1.2.459.gbcd45b4.dirty
WARNING: multiple messages have this Message-ID (diff)
From: Joe Perches <joe@perches.com>
To: linux-kernel@vger.kernel.org
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>,
linuxppc-dev@lists.ozlabs.org
Subject: [PATCH 0/2] powerpc: pci-ioda: Neatening
Date: Sun, 21 Sep 2014 10:55:04 -0700 [thread overview]
Message-ID: <cover.1411320262.git.joe@perches.com> (raw)
printk calls should return void
Joe Perches (2):
powerpc: pci-ioda: Remove unnecessary return value from printk
powerpc: pci-ioda: Use a single function to emit logging messages
(compiled/untested)
arch/powerpc/platforms/powernv/pci-ioda.c | 61 +++++++++++++++----------------
1 file changed, 30 insertions(+), 31 deletions(-)
--
1.8.1.2.459.gbcd45b4.dirty
next reply other threads:[~2014-09-21 18:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-21 17:55 Joe Perches [this message]
2014-09-21 17:55 ` [PATCH 0/2] powerpc: pci-ioda: Neatening Joe Perches
2014-09-21 17:55 ` [PATCH 1/2] powerpc: pci-ioda: Remove unnecessary return value from printk Joe Perches
2014-09-21 17:55 ` Joe Perches
2014-09-21 17:55 ` [PATCH 2/2] powerpc: pci-ioda: Use a single function to emit logging messages Joe Perches
2014-09-21 17:55 ` Joe Perches
2014-09-22 6:56 ` [PATCH 0/2] powerpc: pci-ioda: Neatening Michael Ellerman
2014-09-22 6:56 ` Michael Ellerman
2014-09-23 0:53 ` Gavin Shan
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.1411320262.git.joe@perches.com \
--to=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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 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.