linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Rientjes <rientjes@google.com>
To: Andrew Jones <drjones@redhat.com>
Cc: Jerome Marchand <jmarchan@redhat.com>,
	Arnd Bergmann <arnd@arndb.de>,
	akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	mingo@elte.hu, david.woodhouse@intel.com, gregkh@suse.de,
	davem@davemloft.net, axboe@kernel.dk, holt@sgi.com,
	linux-arch@vger.kernel.org, linux@arm.linux.org.uk,
	hskinnemoen@gmail.com, egtvedt@samfundet.no, msalter@redhat.com,
	a-jacquiot@ti.com, starvik@axis.com, jesper.nilsson@axis.com,
	dhowells@redhat.com, takata@linux-m32r.org, geert@linux-m68k.org,
	yasutake.koichi@jp.panasonic.com, jonas@southpole.se,
	kyle@mcmartin.ca, deller@gmx.de, jejb@parisc-linux.org,
	chris@zankel.net, greg@kroah.com, davej@redhat.com,
	airlied@linux.ie, jkosina@suse.cz, mchehab@infradead.org,
	johannes@sipsolutions.net, linville@tuxdriver.com
Subject: Re: [PATCH] kconfig: untangle EXPERT and EMBEDDED
Date: Wed, 18 Jan 2012 01:31:30 -0800 (PST)	[thread overview]
Message-ID: <alpine.DEB.2.00.1201180119550.19730@chino.kir.corp.google.com> (raw)
In-Reply-To: <20120118085620.GB2317@turtle.usersys.redhat.com>

On Wed, 18 Jan 2012, Andrew Jones wrote:

> > > diff --git a/drivers/hid/Kconfig b/drivers/hid/Kconfig
> > > index a421abd..73c2d39 100644
> > > --- a/drivers/hid/Kconfig
> > > +++ b/drivers/hid/Kconfig
> > > @@ -63,7 +63,7 @@ menu "Special HID drivers"
> > >  config HID_A4TECH
> > >         tristate "A4 tech mice" if EXPERT
> > >         depends on USB_HID
> > > -       default !EXPERT
> > > +       default !EMBEDDED
> > >         ---help---
> > >         Support for A4 tech X5 and WOP-35 / Trust 450L mice.
> > > 
> > > and the other HID drivers...
> > > 
> > 
> > Um, no, HID_A4TECH is still only configurable for CONFIG_EXPERT with this 
> > patch.  Jerome's premise is that this should be configurable for 
> > CONFIG_EMBEDDED instead.  Please read what he wrote.
> 
> Yes, you still need EXPERT to expose the option, but then EMBEDDED will
> switch the default. You only need to set EMBEDDED=y to do that though,
> that's what this little thing called "select" does.
> 

Until such time as EMBEDDED is decoupled from EXPERT.  So to preserve the 
eventual goal of separating EMBEDDED and EXPERT entirely, this would need 
to be a tristate if EXPERT || EMBEDDED.  I'll leave the determination of 
the default to the HID maintainers, it's not my area.

This isn't the first time that Jiri will have had to deal with 
CONFIG_EXPERT usage in this subsystem.

There're other examples of this for x86 for things like serio drivers or 
keyboard drivers.

> Oh, so now we can break backwards compatibility for some cases? What is
> the criteria for those cases? Let me guess at a few;
> 

I think it's fine to break backwards compatibility for options that are 
currently configurable for CONFIG_EXPERT when it only makes sense for 
embedded systems and use CONFIG_EMBEDDED instead.  They better already 
have it enabled and my patch a year ago didn't break it for them.

CONFIG_EXPERT isn't an invitation to be able to configure everything in 
the kernel.

> What do you mean you've considered not reading this pointless thread? You
> wrote it! All the nonsense comes from you. Besides the patch submission,
> which fixes a real problem, this thread HAS been pointless, and wasted a
> lot of my time.
> 

I'm trying to clue you into how we don't break existing configs for users 
who would run make oldconfig on a kernel with your patch.  That's why it's 
nacked and nobody would sanely apply such a patch.

I'll leave the remainder of the thread to you now, thanks.

  reply	other threads:[~2012-01-18  9:31 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-11 15:16 [PATCH] kconfig: untangle EXPERT and EMBEDDED Andrew Jones
2012-01-11 21:57 ` David Rientjes
2012-01-12  9:18   ` Arnd Bergmann
2012-01-12 10:18     ` Andrew Jones
2012-01-12 21:06       ` David Rientjes
2012-01-13  8:51         ` Andrew Jones
2012-01-13 10:53           ` David Rientjes
2012-01-13 12:22             ` Andrew Jones
2012-01-13 21:27               ` David Rientjes
2012-01-16  9:20                 ` Andrew Jones
2012-01-16 23:28                   ` David Rientjes
2012-01-17 14:27                     ` Andrew Jones
2012-01-17 20:46                       ` David Rientjes
2012-01-18  8:14                         ` Andrew Jones
2012-01-18  9:19                           ` David Rientjes
2012-01-16 15:31                 ` Jerome Marchand
2012-01-16 23:37                   ` David Rientjes
2012-01-17 14:46                     ` Andrew Jones
2012-01-17 20:54                       ` David Rientjes
2012-01-18  8:51                         ` Jerome Marchand
2012-01-18  8:56                         ` Andrew Jones
2012-01-18  9:31                           ` David Rientjes [this message]
2012-01-18  9:54                             ` Andrew Jones
2012-01-18  9:38                         ` Andrew Jones
2012-01-12 20:59     ` David Rientjes
2012-01-16 15:40 ` Jerome Marchand
2012-01-16 15:50   ` Andrew Jones
2012-01-16 17:34     ` Geert Uytterhoeven
2012-01-17  8:28       ` Andrew Jones
2012-01-18 11:08 ` Andrew Jones
2012-01-18 20:28   ` Andrew Morton
2012-01-18 20:46     ` Russell King - ARM Linux
2012-01-18 21:04     ` Alexey Dobriyan
2012-01-18 21:36       ` Andrew Morton
2012-01-18 21:48     ` Paul Bolle
2012-01-18 21:55       ` Andrew Morton
2012-01-18 22:13         ` Russell King - ARM Linux
2012-01-18 22:06       ` Alexey Dobriyan
2012-01-18 22:13       ` Dave Jones
2012-01-19  8:09     ` Andrew Jones
2012-01-23 13:46     ` Andrew Jones
2012-01-24  0:43       ` David Rientjes

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=alpine.DEB.2.00.1201180119550.19730@chino.kir.corp.google.com \
    --to=rientjes@google.com \
    --cc=a-jacquiot@ti.com \
    --cc=airlied@linux.ie \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=axboe@kernel.dk \
    --cc=chris@zankel.net \
    --cc=davej@redhat.com \
    --cc=davem@davemloft.net \
    --cc=david.woodhouse@intel.com \
    --cc=deller@gmx.de \
    --cc=dhowells@redhat.com \
    --cc=drjones@redhat.com \
    --cc=egtvedt@samfundet.no \
    --cc=geert@linux-m68k.org \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=holt@sgi.com \
    --cc=hskinnemoen@gmail.com \
    --cc=jejb@parisc-linux.org \
    --cc=jesper.nilsson@axis.com \
    --cc=jkosina@suse.cz \
    --cc=jmarchan@redhat.com \
    --cc=johannes@sipsolutions.net \
    --cc=jonas@southpole.se \
    --cc=kyle@mcmartin.ca \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=linville@tuxdriver.com \
    --cc=mchehab@infradead.org \
    --cc=mingo@elte.hu \
    --cc=msalter@redhat.com \
    --cc=starvik@axis.com \
    --cc=takata@linux-m32r.org \
    --cc=yasutake.koichi@jp.panasonic.com \
    /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;
as well as URLs for NNTP newsgroup(s).