From: Joe Perches <joe@perches.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
linux-kernel@vger.kernel.org,
"Russell King - ARM Linux" <linux@arm.linux.org.uk>,
kernel@pengutronix.de, "Arjan van de Ven" <arjan@infradead.org>,
linux-mm@kvack.org
Subject: Re: [PATCH 5/6] mm: add some KERN_CONT markers to continuation lines
Date: Tue, 01 Mar 2011 21:28:00 -0800 [thread overview]
Message-ID: <1299043680.4208.97.camel@Joe-Laptop> (raw)
In-Reply-To: <AANLkTi=VB5po9Yt2oCcCq01UNQxXNY+_6RBpjWRFkvxN@mail.gmail.com>
On Tue, 2011-03-01 at 13:46 -0800, Linus Torvalds wrote:
> the concept of
> printk(KERN_CONT "\n")
> is just crazy: you're saying "I want to continue the line, in order to
> print a newline". Whaa?
It's a trivially useful "end of collected printk" mark,
which was made a bit superfluous by the code that added
any necessary newline before every KERN_<level>.
There are a thousand or so of them today.
$ grep -rP --include=*.[ch] "\b(printk\s*\(\s*KERN_CONT|pr_cont\s*\(|printk\s*\()\s*\"\\\n\"" * | wc -l
1061
That code made all message terminating newlines a bit
obsolete. I won't be submitting any patches to remove
those EOM newlines any time soon.
I hope no one does that.
It would be actually useful to have some form like:
cookie = collected_printk_start()
loop:
collected_printk(cookie, ...) (...)
collected_printk_end(cookie)
so that interleaved messages from multiple
concurrent streams could be sensibly collected
either post processed or buffered.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2011-03-02 5:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20101124085645.GW4693@pengutronix.de>
2010-11-24 8:57 ` Uwe Kleine-König
2011-02-28 15:17 ` Uwe Kleine-König
2011-03-01 21:46 ` Linus Torvalds
2011-03-02 5:28 ` Joe Perches [this message]
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=1299043680.4208.97.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=arjan@infradead.org \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@arm.linux.org.uk \
--cc=torvalds@linux-foundation.org \
--cc=u.kleine-koenig@pengutronix.de \
/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