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 0/5] printk: more log flag simplification
Date: Thu, 17 Jul 2014 12:59:08 -0500 [thread overview]
Message-ID: <1405619953-5475-1-git-send-email-elder@linaro.org> (raw)
This series rearranges the log code in such a way that the LOG_CONT
and LOG_PREFIX log record flags can be eliminated entirely. The
result should be considerably easier to understand than before. It
builds on another recently-posted series of patches:
https://lkml.org/lkml/2014/7/17/363
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 next three patches together eliminate LOG_PREFIX. The effect
of LOG_PREFIX is to complete the previous log entry before recording
a new one. Patch 2 arranges to do this directly, marking the previous
log record with LOG_NEWLINE whenever a new record is presented with
LOG_PREFIX set. Patch 3 stops saving LOG_PREFIX in any log records,
and patch 4 finally gets rid of LOG_PREFIX.
The last patch is just some cleanup of the code 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
It is based on branch review/printk-flags-v2 in that same repository.
Alex Elder (5):
printk: kill LOG_CONT
printk: update previous message for LOG_PREFIX
printk: stop actually recording LOG_PREFIX
printk: kill LOG_PREFIX
printk: rename LOG_NEWLINE and tidy up
kernel/printk/printk.c | 135 +++++++++++++++++++++++++++++--------------------
1 file changed, 81 insertions(+), 54 deletions(-)
--
1.9.1
next reply other threads:[~2014-07-17 17:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 17:59 Alex Elder [this message]
2014-07-17 17:59 ` [PATCH 1/5] printk: kill LOG_CONT Alex Elder
2014-07-17 17:59 ` [PATCH 2/5] printk: update previous message for LOG_PREFIX Alex Elder
2014-07-18 9:02 ` Petr Mládek
2014-07-18 12:04 ` Alex Elder
2014-07-17 17:59 ` [PATCH 3/5] printk: stop actually recording LOG_PREFIX Alex Elder
2014-07-17 17:59 ` [PATCH 4/5] printk: kill LOG_PREFIX Alex Elder
2014-07-17 17:59 ` [PATCH 5/5] printk: rename LOG_NEWLINE and tidy up Alex Elder
2014-07-18 1:37 ` [PATCH 0/5] printk: more log flag simplification Kay Sievers
2014-07-18 1:54 ` Alex Elder
2014-07-18 9:22 ` Petr Mládek
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=1405619953-5475-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