From: SF Markus Elfring <elfring@users.sourceforge.net>
To: trivial@kernel.org, Geert Uytterhoeven <geert+renesas@glider.be>
Cc: LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org
Subject: [PATCH 0/6] FRV-setup: Fine-tuning for six function implementations
Date: Fri, 21 Oct 2016 07:03:27 +0200 [thread overview]
Message-ID: <1405b16a-c470-531d-458d-fb6042b93230@users.sourceforge.net> (raw)
From: Markus Elfring <elfring@users.sourceforge.net>
Date: Thu, 20 Oct 2016 22:44:22 +0200
Some update suggestions were taken into account
from static source code analysis.
Markus Elfring (6):
Use seq_puts() in show_cpuinfo()
Use seq_putc() in show_cpuinfo()
Add some spaces for better code readability
Move "else" closer to a brace
Fix indentation in two lines
Move statements for "case" to separate lines
arch/frv/kernel/setup.c | 62 +++++++++++++++++++++++++------------------------
1 file changed, 32 insertions(+), 30 deletions(-)
--
2.10.1
next reply other threads:[~2016-10-21 5:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 5:03 SF Markus Elfring [this message]
2016-10-21 5:05 ` [PATCH 1/6] FRV-setup: Use seq_puts() in show_cpuinfo() SF Markus Elfring
2016-10-21 5:07 ` [PATCH 2/6] FRV-setup: Use seq_putc() " SF Markus Elfring
2016-10-21 5:08 ` [PATCH 3/6] FRV-setup: Add some spaces for better code readability SF Markus Elfring
2016-10-21 5:09 ` [PATCH 4/6] FRV-setup: Move "else" closer to a brace SF Markus Elfring
2016-10-21 5:10 ` [PATCH 5/6] FRV-setup: Fix indentation in two lines SF Markus Elfring
2016-10-21 7:24 ` Jiri Kosina
2016-10-21 7:51 ` Dan Carpenter
2016-10-21 9:11 ` FRV-setup: Clarification for "source code clean-up"? SF Markus Elfring
2016-10-21 9:27 ` Dan Carpenter
2016-10-21 9:50 ` SF Markus Elfring
2016-10-21 10:22 ` Dan Carpenter
2016-10-21 10:28 ` Geert Uytterhoeven
2016-10-21 11:03 ` Julia Lawall
2016-10-21 11:38 ` Improving software around DMA API usage? SF Markus Elfring
2016-10-21 5:11 ` [PATCH 6/6] FRV-setup: Move statements for "case" to separate lines 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=1405b16a-c470-531d-458d-fb6042b93230@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=geert+renesas@glider.be \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@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
Powered by JetHome