public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: linux1394-devel@lists.sourceforge.net,
	Ben Collins <bcollins@debian.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 13/30] Use menuconfig objects - IEEE1394
Date: Sat, 28 Apr 2007 12:41:17 +0200	[thread overview]
Message-ID: <463324CD.1010604@s5r6.in-berlin.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0704280944100.506@yvahk01.tjqt.qr>

Jan Engelhardt wrote:
> On Apr 27 2007 22:56, Stefan Richter wrote:
> 
>>> -config IEEE1394
>>> +menuconfig IEEE1394
>>>  	tristate "IEEE 1394 (FireWire) support"
>>>  	depends on PCI || BROKEN
>>>  	select NET
>> [...]
>>
>> Unless there are objections, I will merge it into my queue of IEEE 1394
>> updates for Linus.
> 
> Yes, I do have objections now that the ieee1394 is different in
> 2.6.21-rc7-mm1.
> Now you have two options in the firewire menu, namely the new
> stack and the old stack. Then menuconfig is not really suitable
> anymore.
> So please skip it until the old stack finds its way out (which may
> take some more time, yes).

My idea, which I planned to cast into a patch during this weekend, was
to keep a patch in linux1394-2.6.git's feed to -mm which basically
restores what can now be seen in -mm  (one 1394 menu, two big
subsections in it), while Linus' tree gets the menuconfig form.

On the other hand, there may come a period were Linus' tree gets
something like we have in -mm, i.e. the choice to enable one or the
other or both or none of the two stacks.

So, shall I put Jan's patch aside until there is only one stack left?

Or what about:

	menuconfig FIREWIRE_SUPPORT
		tristate "IEEE 1394 (FireWire) support"

	config FIREWIRE
		tristate "new FireWire stack, alias Juju"
		depends on FIREWIRE_SUPPORT && !(IEEE1394=y)
		default m
	[...]

	config IEEE1394
		tristate "legacy FireWire stack"
		depends on FIREWIRE_SUPPORT && !(FIREWIRE=y)
		default m
	[...]

	comment "You can have both stacks installed but should blacklist
	         the modules of one of them.  Else modules from both
	         stacks will be autoloaded on hotplug events."
		depends on FIREWIRE && IEEE1394

(Untested pseudo code.)  This would add an extra level of yes/no/m
choice for those who want FireWire drivers.  But it lets people who
don't want FireWire skip everything at the superordinate menu.
-- 
Stefan Richter
-=====-=-=== -=-- ===--
http://arcgraph.de/sr/

  reply	other threads:[~2007-04-28 10:41 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-10 19:17 [PATCH 0/30] Use menuconfig objects Jan Engelhardt
2007-04-10 19:22 ` [PATCH 01/30] Use menuconfig objects - ACPI Jan Engelhardt
2007-04-10 19:48 ` [PATCH 02/30] Use menuconfig objects - APM Jan Engelhardt
2007-04-10 19:50 ` [PATCH 03/30] Use menuconfig objects - libata Jan Engelhardt
2007-04-10 19:52 ` [PATCH 04/30] Use menuconfig objects - block layer Jan Engelhardt
2007-04-10 19:53 ` [PATCH 05/30] Use menuconfig objects - connector Jan Engelhardt
2007-04-11  7:24   ` Evgeniy Polyakov
2007-04-10 20:45 ` [PATCH 06/30] Use menuconfig objects - crypto Jan Engelhardt
2007-04-10 20:46 ` [PATCH 07/30] Use menuconfig objects - crypto hw Jan Engelhardt
2007-04-10 21:07 ` [PATCH 08/30] Use menuconfig objects - DCCP Jan Engelhardt
2007-04-10 21:10 ` [PATCH 09/30] Use menuconfig objects - fusion Jan Engelhardt
2007-04-10 21:11 ` [PATCH 10/30] Use menuconfig objects - I2C Jan Engelhardt
2007-04-11  8:14   ` Jean Delvare
2007-04-11  8:32     ` Jan Engelhardt
2007-04-11 12:28       ` [PATCH 10/30 #2] " Jan Engelhardt
2007-04-13  9:04         ` Jean Delvare
2007-04-10 21:13 ` [PATCH 11/30] Use menuconfig objects - I2O Jan Engelhardt
2007-04-10 21:14 ` [PATCH 12/30] Use menuconfig objects - IDE Jan Engelhardt
2007-04-10 21:17 ` [PATCH 13/30] Use menuconfig objects - IEEE1394 Jan Engelhardt
2007-04-10 22:21   ` Stefan Richter
2007-04-27 20:56   ` Stefan Richter
2007-04-28  7:47     ` Jan Engelhardt
2007-04-28 10:41       ` Stefan Richter [this message]
2007-04-28 10:57         ` Jan Engelhardt
2007-04-28 11:37           ` Stefan Richter
2007-04-29 13:01             ` Jan Engelhardt
2007-04-10 21:18 ` [PATCH 14/30] Use menuconfig objects - MD Jan Engelhardt
2007-04-10 21:22 ` [PATCH 15/30] Use menuconfig objects - module menu Jan Engelhardt
2007-04-10 21:22 ` [PATCH 16/30] Use menuconfig objects - MTD Jan Engelhardt
2007-04-10 21:25 ` [PATCH 17/30] Use menuconfig objects - IPVS Jan Engelhardt
2007-04-11  4:55   ` Simon Horman
2007-04-10 21:26 ` [PATCH 18/30] Use menuconfig objects - SCTP Jan Engelhardt
2007-04-10 21:27 ` [PATCH 19/30] Use menuconfig objects - TIPC Jan Engelhardt
2007-04-10 21:31 ` [PATCH 20/30] Use menuconfig objects - ARCNET Jan Engelhardt
2007-04-11  8:30   ` Esben Nielsen
2007-04-11  8:38     ` Jan Engelhardt
2007-04-11  9:10       ` Esben Nielsen
2007-04-10 21:33 ` [PATCH 21/30] Use menuconfig objects - PHY Jan Engelhardt
2007-04-10 21:35 ` [PATCH 22/30] Use menuconfig objects - toeknring Jan Engelhardt
2007-04-10 21:36 ` [PATCH 23/30] Use menuconfig objects - netdev Jan Engelhardt
2007-04-10 21:37 ` [PATCH 24/30] Use menuconfig objects - oldcd Jan Engelhardt
2007-04-11  7:55   ` Jan Engelhardt
2007-04-11  8:12     ` Andrew Morton
2007-04-11 18:53       ` Stefan Richter
2007-04-10 21:39 ` [PATCH 25/30] Use menuconfig objects - parport Jan Engelhardt
2007-04-10 21:40 ` [PATCH 26/30] Use menuconfig objects - pcihotplug Jan Engelhardt
2007-04-10 21:41 ` [PATCH 27/30] Use menuconfig objects - PCMCIA Jan Engelhardt
2007-04-10 21:42 ` [PATCH 28/30] Use menuconfig objects - PNP Jan Engelhardt
2007-04-10 21:42 ` [PATCH 29/30] Use menuconfig objects - SCSI Jan Engelhardt
2007-04-10 21:43 ` [PATCH 30/30] Use menuconfig objects - W1 Jan Engelhardt
2007-04-10 22:04 ` [PATCH 0/30] Use menuconfig objects Stefan Richter
2007-04-10 21:40   ` David Lang
2007-04-10 22:41     ` Stefan Richter
2007-04-10 22:09   ` Jan Engelhardt
2007-04-10 23:19     ` Adrian Bunk
2007-04-11  5:52       ` Robert P. J. Day
2007-04-12 22:50 ` Andrew Morton
2007-04-12 23:07   ` Randy Dunlap
2007-04-12 23:18     ` Jan Engelhardt
2007-04-12 23:30       ` Randy Dunlap
2007-04-12 23:16   ` Jan Engelhardt
2007-04-12 23:35     ` Andrew Morton
2007-04-13  9:50 ` Jean Delvare
2007-04-13 16:02   ` Jan Engelhardt
2007-05-10 22:38 ` Andrew Morton
2007-05-11  6:05   ` Jan Engelhardt
2007-05-11  6:18     ` Andrew Morton
2007-05-11  7:47       ` Jan Engelhardt

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=463324CD.1010604@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=bcollins@debian.org \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    /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