public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Jody McIntyre <scjody@modernduck.com>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] update the i386 defconfig
Date: Tue, 24 Jan 2006 00:54:16 +0100	[thread overview]
Message-ID: <20060123235416.GD3590@stusta.de> (raw)
In-Reply-To: <20060120040326.GF13178@conscoop.ottawa.on.ca>

On Thu, Jan 19, 2006 at 11:03:27PM -0500, Jody McIntyre wrote:
> On Thu, Jan 19, 2006 at 09:10:46PM +0100, Adrian Bunk wrote:
> > [...]
> >  #
> >  # IEEE 1394 (FireWire) support
> >  #
> > -CONFIG_IEEE1394=y
> 
> Boo.  1394 good.  I suggest the above plus:
> 
> CONFIG_IEEE1394_SBP2=y
> CONFIG_IEEE1394_RAWIO=y

As the patch description said, the i386 defconfig hasn't been updated 
for some time, and I'm therefore updating it with the semantics "the 
kernel that successfully runs on my computer".

I have no problem if someone wants to maintain the i386 defconfig with a 
different semantics, but as long as noone steps up to maintain it, 
I plan to occasionally update it with the semantics "my .config".

> Cheers,
> Jody

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  parent reply	other threads:[~2006-01-23 23:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-19 20:10 [2.6 patch] update the i386 defconfig Adrian Bunk
2006-01-20  4:03 ` Jody McIntyre
2006-01-20 14:35   ` Jan Engelhardt
2006-01-20 14:41     ` Jody McIntyre
2006-01-23 23:54   ` Adrian Bunk [this message]
2006-01-24  2:24     ` Jody McIntyre
2006-01-24 22:19       ` Adrian Bunk

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=20060123235416.GD3590@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=scjody@modernduck.com \
    --cc=torvalds@osdl.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