From: Alex Elder <elder@linaro.org>
To: akpm@linux-foundation.org
Cc: kay@vrfy.org, pmladek@suse.cz, bp@suse.de,
john.stultz@linaro.org, jack@suse.cz,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] printk: more log flag simplification
Date: Tue, 22 Jul 2014 09:01:55 -0500 [thread overview]
Message-ID: <1406037717-9670-1-git-send-email-elder@linaro.org> (raw)
This series eliminates the LOG_CONT entirely from the printk/log code.
It builds on another series, posted earlier today:
http://www.spinics.net/lists/kernel/msg1791665.html
This series was originally longer, but in review I was reminded
that some of the simplifications I had done were not valid.
The first patch exploits the fact that LOG_CONT and LOG_NEWLINE
are inverses, and uses LOG_NEWLINE (or its negation) anywhere
LOG_CONT is used. As a result, LOG_CONT is no longer needed, so
it's eliminated.
The second patch improves some comments and makes a few small
code cleanups, now that it's gone through this transformation.
-Alex
This series is available here:
http://git.linaro.org/landing-teams/working/broadcom/kernel.git
Branch review/more-printk-flags-v2
It is based on branch review/printk-flags-v6 in that same repository.
Alex Elder (2):
printk: kill LOG_CONT
printk: improve some commentary; tidy up
kernel/printk/printk.c | 99 ++++++++++++++++++++++++++++++--------------------
1 file changed, 59 insertions(+), 40 deletions(-)
--
1.9.1
next reply other threads:[~2014-07-22 14:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 14:01 Alex Elder [this message]
2014-07-22 14:01 ` [PATCH v2 1/2] printk: kill LOG_CONT Alex Elder
2014-07-22 14:01 ` [PATCH v2 2/2] printk: improve some commentary; tidy up Alex Elder
2014-07-22 14:24 ` [PATCH v2 0/2] printk: more log flag simplification Borislav Petkov
2014-07-22 15:55 ` Alex Elder
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=1406037717-9670-1-git-send-email-elder@linaro.org \
--to=elder@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=bp@suse.de \
--cc=jack@suse.cz \
--cc=john.stultz@linaro.org \
--cc=kay@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.cz \
/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