From: "Luis R. Rodriguez" <mcgrof@suse.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] printk: Don't bother using LOG_CPU_MAX_BUF_SHIFT on !SMP
Date: Fri, 8 Aug 2014 17:34:02 +0200 [thread overview]
Message-ID: <20140808153402.GE21930@wotan.suse.de> (raw)
In-Reply-To: <1407511244-5332-1-git-send-email-geert@linux-m68k.org>
On Fri, Aug 08, 2014 at 05:20:44PM +0200, Geert Uytterhoeven wrote:
> When configuring a uniprocessor kernel, don't bother the user with an
> irrelevant LOG_CPU_MAX_BUF_SHIFT question, and don't build the unused
> code.
>
> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
Acked-by: Luis R. Rodriguez <mcgrof@suse.com>
Luis
prev parent reply other threads:[~2014-08-08 15:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 15:20 Geert Uytterhoeven
2014-08-08 15:34 ` Luis R. Rodriguez [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=20140808153402.GE21930@wotan.suse.de \
--to=mcgrof@suse.com \
--cc=akpm@linux-foundation.org \
--cc=geert@linux-m68k.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
all inboxes | Powered by JetHome®