LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: "Jan Beulich" <jbeulich@novell.com>
Cc: "Roman Zippel" <zippel@linux-m68k.org>,
	"lkml" <linux-kernel@vger.kernel.org>,
	"Randy Dunlap" <rdunlap@xenotime.net>
Subject: Re: 2.6.23-git Kconfig regression
Date: Thu, 17 Jan 2008 00:32:54 -0800	[thread overview]
Message-ID: <200801170032.54788.david-b@pacbell.net> (raw)
In-Reply-To: <478F1CDD.76E4.0078.0@novell.com>

On Thursday 17 January 2008, Jan Beulich wrote:
> >This stuff isn't for "distro" kernels; it's for embedded
> >environments of the "only this hardware exists" sort.
> >Space matters, and having small code matters.  Nobody has
> >been interested enough in an "embedded distro" model to
> >provide patches enabling such stuff.
> 
> Why not make the whole thing depend on EMBEDDED then?

Because while its design center is small systems, there's
actually no technical dependency there.  The Kconfig for
EMBEDDED also says it's for disabling or tweaking standard
settings ... ergo, not *adding* subsystems or drivers.

Oddly enough, most things that work on small systems can
also be used on bigger ones.  :)

- Dave

  reply	other threads:[~2008-01-17  8:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-20  1:22 David Brownell
2007-10-20  1:46 ` Randy Dunlap
2007-10-20  1:57   ` David Brownell
2007-10-20  2:01     ` Randy Dunlap
2007-10-20  2:55       ` Randy Dunlap
2007-10-20  3:21         ` Randy Dunlap
2007-10-20  4:11           ` David Brownell
2007-10-20  4:25             ` Linus Torvalds
2007-10-20 16:50               ` Sam Ravnborg
2008-01-16  9:29           ` Jan Beulich
2008-01-17  0:02             ` David Brownell
2008-01-17  8:16               ` Jan Beulich
2008-01-17  8:32                 ` David Brownell [this message]
2007-10-20 18:27 Jan Beulich

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=200801170032.54788.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=jbeulich@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=zippel@linux-m68k.org \
    --subject='Re: 2.6.23-git Kconfig regression' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).