public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Metcalf <cmetcalf@tilera.com>
To: Joe Perches <joe@perches.com>, Davidlohr Bueso <davidlohr@hp.com>
Cc: "Petr Mládek" <pmladek@suse.cz>,
	"Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
	linux-kernel@vger.kernel.org,
	"Luis R. Rodriguez" <mcgrof@suse.com>,
	"Michal Hocko" <mhocko@suse.cz>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Arun KS" <arunks.linux@gmail.com>,
	"Kees Cook" <keescook@chromium.org>
Subject: Re: [RFC] printk: allow increasing the ring buffer depending on the number of CPUs
Date: Mon, 16 Jun 2014 16:17:36 -0400	[thread overview]
Message-ID: <539F50E0.3030900@tilera.com> (raw)
In-Reply-To: <1402598718.12385.16.camel@joe-AO725>

On 6/12/2014 2:45 PM, Joe Perches wrote:
> (adding Chris Metcalf for arch/tile,
>   I think this change might impact that arch)

Thanks for the Cc.  I've been following the discussion and I think it's on the right track for arch/tile.

-- 
Chris Metcalf, Tilera Corp.
http://www.tilera.com


  parent reply	other threads:[~2014-06-16 20:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-11  1:04 [RFC] printk: allow increasing the ring buffer depending on the number of CPUs Luis R. Rodriguez
2014-06-11  9:34 ` Petr Mládek
2014-06-11 21:47   ` Luis R. Rodriguez
2014-06-12 13:05     ` Petr Mládek
2014-06-12 20:22       ` Luis R. Rodriguez
2014-06-12 18:01   ` Davidlohr Bueso
2014-06-12 18:45     ` Joe Perches
2014-06-12 21:28       ` Luis R. Rodriguez
2014-06-16 20:17       ` Chris Metcalf [this message]
2014-06-12 21:12     ` Luis R. Rodriguez

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=539F50E0.3030900@tilera.com \
    --to=cmetcalf@tilera.com \
    --cc=akpm@linux-foundation.org \
    --cc=arunks.linux@gmail.com \
    --cc=davidlohr@hp.com \
    --cc=joe@perches.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@do-not-panic.com \
    --cc=mcgrof@suse.com \
    --cc=mhocko@suse.cz \
    --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