All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] move LOG_BUF_SIZE to header file
Date: Tue, 17 Dec 2002 09:27:03 -0800	[thread overview]
Message-ID: <3DFF5E67.C0BA874C@digeo.com> (raw)
In-Reply-To: Pine.LNX.4.33L2.0212121517300.19827-100000@dragon.pdx.osdl.net

"Randy.Dunlap" wrote:
> 
> ...
> One other thing that I considered doing was using a common
> Kconfig file for all 20 arch'es by adding a
>   source "kernel/Kconfig"
> at the end of each <arch>/Kconfig file.  This would provide
> a common "General setup (more)" that could be used after most
> config options are set instead of near the top of the menu.
> Does that make sense to anybody?
> 

I think so.  There are times when one wants to add arch-neutral
config items which just don't logically fit into any of the
existing menus.  The right place to put the item is into each
and every architecture's arch/<arch>/Kconfig, and that's plain
silly.

  parent reply	other threads:[~2002-12-17 17:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-10 19:16 move LOG_BUF_SIZE to header file Randy.Dunlap
2002-12-10 19:41 ` Andrew Morton
2002-12-17  6:11   ` [PATCH] " Randy.Dunlap
2002-12-17  6:39     ` James H. Cloos Jr.
2002-12-17 17:22       ` Randy.Dunlap
2002-12-17  9:41     ` Christoph Hellwig
2002-12-17 17:14       ` Randy.Dunlap
2002-12-17 17:27     ` Andrew Morton [this message]
2002-12-17 22:33       ` [PATCH] (v3) move LOG_BUF_SIZE to header/config Randy.Dunlap
2002-12-18  1:14         ` Andrew Morton
2002-12-18  4:03           ` Randy.Dunlap

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=3DFF5E67.C0BA874C@digeo.com \
    --to=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.