All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Ingo Molnar <mingo@elte.hu>,
	Stephen Hemminger <shemminger@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Jan Engelhardt <jengelh@gmx.de>,
	Richard Purdie <rpurdie@rpsys.net>,
	Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [patch, -git] input: CONFIG_INPUT_APANEL build fix
Date: Wed, 30 Apr 2008 22:36:42 -0400	[thread overview]
Message-ID: <20080501023642.GA7063@anvil.corenet.prv> (raw)
In-Reply-To: <Pine.LNX.4.64.0805010213530.30555@scrub.home>

Hi Roman,

On Thu, May 01, 2008 at 02:51:47AM +0200, Roman Zippel wrote:
> Hi,
> 
> On Wed, 30 Apr 2008, Dmitry Torokhov wrote:
> 
> > You still did not answer to the main question - do you think we should
> > revert the commit that actually introduced breakage in the sense that
> > anything depending on LEDS_CLASS should also add NEW_LEDS dependancy?
> > That will take care of the problem (as far as LEDs are concerned) for
> > _all_ subsystems and drivers at once.
> 
> Well, that would mean reverting the complete led subsystem, since the 
> menuconfig patch you pointed at, isn't really the problem (did you 
> actually try to revert that patch?).
> 

Yes, I did. The revert fixed the apanel driver which does not select
but rather "depends on" LEDS_CLASS for me.

> Anyway, the actual issue are all the drivers that select LEDS_CLASS
> without selecting NEW_LEDS.
>

This is a different issue from the original reported one.
 
> The patch below fixes the dependency problem without adding a lot of new 
> selects by using LEDS_CORE, which is selected by LEDS_CLASS/LEDS_TRIGGERS 
> as needed.
> I removed the comments as they were a little redundant and I removed the 
> selects of NEW_LEDS as these are not needed anymore.
> 
> Signed-off-by: Roman Zippel <zippel@linux-m68k.org>
> 

The patch appears to fix both problems at once (select and depends on + if),
I like it. Could we please have it applied to mainline, please?

BTW, does this mean that all 'if'-guarded symbols should be converted to
this style?

-- 
Dmitry

  reply	other threads:[~2008-05-01  2:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-30 18:54 [patch, -git] input: CONFIG_INPUT_APANEL build fix Ingo Molnar
2008-04-30 19:04 ` Dmitry Torokhov
2008-04-30 20:20   ` Ingo Molnar
2008-04-30 20:56     ` Roman Zippel
2008-04-30 22:21       ` Dmitry Torokhov
2008-04-30 21:00     ` Dmitry Torokhov
2008-04-30 21:20       ` Ingo Molnar
2008-04-30 22:26         ` Dmitry Torokhov
2008-04-30 22:38           ` Ingo Molnar
2008-04-30 22:47             ` Dmitry Torokhov
2008-05-01  0:51               ` Roman Zippel
2008-05-01  2:36                 ` Dmitry Torokhov [this message]
2008-05-01  6:25                   ` Jan Engelhardt
2008-05-01  1:29               ` Ingo Molnar

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=20080501023642.GA7063@anvil.corenet.prv \
    --to=dmitry.torokhov@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=jengelh@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rpurdie@rpsys.net \
    --cc=sam@ravnborg.org \
    --cc=shemminger@linux-foundation.org \
    --cc=zippel@linux-m68k.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.