From: SF Markus Elfring <elfring@users.sourceforge.net>
To: adi-buildroot-devel@lists.sourceforge.net,
Rickard Strandqvist <rickard_strandqvist@spectrumdigital.se>,
Steven Miao <realmz6@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org
Subject: [PATCH 0/5] Blackfin: Fine-tuning for three function implementations
Date: Wed, 19 Oct 2016 22:44:52 +0200 [thread overview]
Message-ID: <4cd6678e-ebf0-d2f4-0b79-ac33060a6752@users.sourceforge.net> (raw)
From: Markus Elfring <elfring@users.sourceforge.net>
Date: Wed, 19 Oct 2016 22:24:22 +0200
A few update suggestions were taken into account
from static source code analysis.
Markus Elfring (5):
cplbinfo: Use seq_puts() in cplbinfo_print_header()
irqchip: Combine two seq_printf() calls into one call in arch_show_interrupts()
setup: Use seq_putc() in show_cpuinfo()
setup: Replace three seq_printf() calls by seq_puts() in show_cpuinfo()
setup: Combine ten seq_printf() calls into three calls in show_cpuinfo()
arch/blackfin/kernel/cplbinfo.c | 3 +-
arch/blackfin/kernel/irqchip.c | 6 ++--
arch/blackfin/kernel/setup.c | 73 ++++++++++++++++++++++-------------------
3 files changed, 46 insertions(+), 36 deletions(-)
--
2.10.1
next reply other threads:[~2016-10-19 20:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 20:44 SF Markus Elfring [this message]
2016-10-19 20:46 ` [PATCH 1/5] blackfin-cplbinfo: Use seq_puts() in cplbinfo_print_header() SF Markus Elfring
2016-10-19 20:47 ` [PATCH 2/5] blackfin-irqchip: Combine two seq_printf() calls into one call in arch_show_interrupts() SF Markus Elfring
2016-10-19 20:48 ` [PATCH 3/5] blackfin-setup: Use seq_putc() in show_cpuinfo() SF Markus Elfring
2016-10-19 20:49 ` [PATCH 4/5] blackfin-setup: Replace three seq_printf() calls by seq_puts() " SF Markus Elfring
2016-10-19 20:50 ` [PATCH 5/5] blackfin-setup: Combine ten seq_printf() calls into three calls " SF Markus Elfring
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=4cd6678e-ebf0-d2f4-0b79-ac33060a6752@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=adi-buildroot-devel@lists.sourceforge.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=realmz6@gmail.com \
--cc=rickard_strandqvist@spectrumdigital.se \
/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
Powered by JetHome