From: Joe Perches <joe@perches.com>
To: Tejun Heo <tj@kernel.org>
Cc: Christoph Lameter <cl@linux-foundation.org>,
linux-kernel@vger.kernel.org, Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: [PATCH] percpu: use KERN_CONT in pcpu_dump_alloc_info()
Date: Thu, 29 Mar 2012 13:06:56 -0700 [thread overview]
Message-ID: <1333051616.15602.23.camel@joe2Laptop> (raw)
In-Reply-To: <CAOS58YOWA9U3Esb2535v_iivPaXeFYYS3nWd2KKF1=MsfZ0Piw@mail.gmail.com>
On Thu, 2012-03-29 at 12:51 -0700, Tejun Heo wrote:
> Hello, Joe.
Hello Tejun.
> On Thu, Mar 29, 2012 at 11:10 AM, Joe Perches <joe@perches.com> wrote:
> > Perhaps it's better to try to print lines
> > in fewer printks? Maybe use a line buffer?
> What practical difference would that make?
It'd be just for avoidance of any other possible
interleaving from other threads.
It's an __init function so that's not too likely,
but if it every happens...
next prev parent reply other threads:[~2012-03-29 20:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 16:48 [PATCH] percpu: use KERN_CONT in pcpu_dump_alloc_info() Tejun Heo
2012-03-29 18:10 ` Joe Perches
2012-03-29 19:51 ` Tejun Heo
2012-03-29 20:06 ` Joe Perches [this message]
2012-03-29 20:11 ` Tejun Heo
2012-04-01 13:29 ` Kay Sievers
2012-04-01 14:55 ` Joe Perches
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=1333051616.15602.23.camel@joe2Laptop \
--to=joe@perches.com \
--cc=cl@linux-foundation.org \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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