From: "\"Jan H. Schönherr\"" <schnhrr@cs.tu-berlin.de>
To: Kay Sievers <kay@vrfy.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] printk: drop ambiguous LOG_CONT flag
Date: Thu, 27 Sep 2012 18:04:30 +0200 [thread overview]
Message-ID: <5064790E.4000207@cs.tu-berlin.de> (raw)
In-Reply-To: <506474D0.9020406@cs.tu-berlin.de>
Am 27.09.2012 17:46, schrieb "Jan H. Schönherr":
> If we say "if LOG_CONT is set, this message continues the previous one",
> we can also say "there is no prefix on this message". Then on the other
> hand, we would need a "whatever comes next, it does not continue this
> message"....
Thinking a bit longer about this one.
If really, really everything passes through vprintk_emit()
then we could keep all info about the previous message
there and definitely decide whether the current message continues
the previous one.
Then, we wouldn't need to track the previous flags everywhere.
Do I miss something?
Regards
Jan
next prev parent reply other threads:[~2012-09-27 16:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-26 17:58 [PATCH] printk: drop ambiguous LOG_CONT flag Jan H. Schönherr
2012-09-26 21:15 ` Greg Kroah-Hartman
2012-09-26 22:33 ` "Jan H. Schönherr"
2012-09-27 13:39 ` Kay Sievers
2012-09-27 15:46 ` "Jan H. Schönherr"
2012-09-27 16:04 ` "Jan H. Schönherr" [this message]
2012-09-28 8:25 ` Jan H. Schönherr
2012-09-28 14:34 ` Kay Sievers
2012-09-28 14:49 ` "Jan H. Schönherr"
2012-09-28 14:56 ` Kay Sievers
2012-10-08 19:24 ` Kay Sievers
2012-10-08 19:54 ` "Jan H. Schönherr"
2012-10-08 19:56 ` Kay Sievers
2012-11-02 3:53 ` Kay Sievers
2012-11-02 22:37 ` "Jan H. Schönherr"
2012-11-02 23:36 ` Greg Kroah-Hartman
2012-11-03 21:12 ` [PATCH resend] " Jan H. Schönherr
2012-11-10 18:47 ` "Jan H. Schönherr"
2012-10-08 23:10 ` [PATCH] " Joe Perches
2012-09-28 2:28 ` Kay Sievers
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=5064790E.4000207@cs.tu-berlin.de \
--to=schnhrr@cs.tu-berlin.de \
--cc=gregkh@linuxfoundation.org \
--cc=kay@vrfy.org \
--cc=linux-kernel@vger.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