netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: Simon Horman <horms@verge.net.au>
Cc: "Kim Phillips" <kim.phillips@freescale.com>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	"Ismail Dönmez" <ismail@pardus.org.tr>,
	"Kumar Gala" <galak@kernel.crashing.org>,
	"Michael Schmitz" <schmitz@debian.org>,
	"Roman Zippel" <zippel@linux-m68k.org>,
	"Geert Uytterhoeven" <geert@linux-m68k.org>,
	"Johannes Berg" <johannes@sipsolutions.net>,
	"Benjamin Herrenschmidt" <benh@kernel.crashing.org>,
	"Paul Mackerras" <paulus@samba.org>
Subject: Re: Kconfig warnings on latest GIT
Date: Thu, 10 May 2007 11:56:48 -0500	[thread overview]
Message-ID: <46434ED0.6030808@freescale.com> (raw)
In-Reply-To: <20070510051042.GA16812@verge.net.au>

Simon Horman wrote:

>> So my question is: in which Kconfig do I define "UCC_FAST_TEMP" and 
>> "UCC_SLOW_TEMP"?  At first I thought, just put it in drivers/Kconfig, but that 
>> Kconfig does nothing but including other Kconfigs.  I believe that if I submit 
>> a patch that adds "UCC_FAST_TEMP" and "UCC_SLOW_TEMP" to drivers/Kconfig, it 
>> will be rejected.  Either that, or I'll spend six weeks trying to persuade 
>> everyone that it's a good idea.
>>
>> Does anyone have any suggestions on how I can fix this?
> 
> That does seem like a reasonable suggestion, and one that
> would probably work well with the other similar problems
> that have been introduced sice 2.6.21.

Looks like the fix is simpler than I thought.  Instead of having

UCC_GETH
	select UCC_FAST

I need to do

UCC_FAST
	default y if UCC_GETH

I'll have a patch that fixes this out later today.

I chose the first method because I wanted each individual UCC device driver to select 
UCC_FAST or UCC_SLOW as appropriate, so that I wouldn't have to update 
arch/powerpc/sysdev/qe_lib/Kconfig every time we add a new UCC driver.  Oh well.

-- 
Timur Tabi
Linux Kernel Developer @ Freescale

  parent reply	other threads:[~2007-05-10 16:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-07 21:04 Kconfig warnings on latest GIT Ismail Dönmez
2007-05-08 19:31 ` Kim Phillips
2007-05-08 20:11   ` Timur Tabi
2007-05-10  5:10     ` Simon Horman
2007-05-10 15:39       ` Johannes Berg
2007-05-11  1:22         ` Simon Horman
2007-05-11 11:45           ` Johannes Berg
2007-05-14  1:32             ` Simon Horman
2007-05-14 12:55               ` Johannes Berg
2007-05-14 14:24                 ` Kumar Gala
2007-05-14 16:25                   ` Johannes Berg
2007-05-10 16:56       ` Timur Tabi [this message]
2007-05-11  1:25         ` Simon Horman
2007-05-11  1:41           ` Kumar Gala
2007-05-11  1:47           ` Kumar Gala
2007-05-11  2:05             ` Simon Horman
2007-05-11  2:13               ` Kumar Gala
2007-05-11  2:27                 ` Simon Horman
2007-05-11  2:32                   ` Timur Tabi
2007-05-11  3:08                   ` Simon Horman
2007-05-11  7:43             ` Russell King
2007-05-11 12:38               ` Timur Tabi

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=46434ED0.6030808@freescale.com \
    --to=timur@freescale.com \
    --cc=benh@kernel.crashing.org \
    --cc=galak@kernel.crashing.org \
    --cc=geert@linux-m68k.org \
    --cc=horms@verge.net.au \
    --cc=ismail@pardus.org.tr \
    --cc=johannes@sipsolutions.net \
    --cc=kim.phillips@freescale.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=schmitz@debian.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 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).