From: linas@austin.ibm.com (Linas Vepstas)
To: Olof Johansson <olof@lixom.net>
Cc: linuxppc-dev@ozlabs.org, nfonteno@us.ibm.com,
Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] ppc64_defconfig to use AUTOFS_V4 not V3
Date: Wed, 29 Nov 2006 13:32:27 -0600 [thread overview]
Message-ID: <20061129193227.GO10879@austin.ibm.com> (raw)
In-Reply-To: <20061129124511.3be6b9a8@localhost.localdomain>
On Wed, Nov 29, 2006 at 12:45:11PM -0600, Olof Johansson wrote:
> On Wed, 29 Nov 2006 12:05:22 -0600 linas@austin.ibm.com (Linas Vepstas) wrote:
>
> > Please apply. Although I have a general question: who is served
> > by the ppc64_defconfig these days? Any reason why its not more
> > like powerpc_defcofig? "make defconfig" uses uname -m to pick up
> > the defconfig, and my cell, rhel5 and sles10 boxes report ppc64
> > not pseries for uname -m.
>
> I like using it to build a kernel that runs on as much as possible with
> a single image, but I don't think all platforms have been added there
> (yet). Sort of like a superset of all other 64-bit configs.
Ahh, well, in that case, I propsoe turning on the following as well.
CONFIG_USB_MON=y
CONFIG_FUSE_FS=m
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_ZISOFS_FS=y
CONFIG_XMON_DEFAULT=y
and a few device drivers:
CONFIG_IXGB_NAPI=y
CONFIG_S2IO=m
CONFIG_S2IO_NAPI=y
I had mistook ppc64 as being subset-ish not superset-ish.
--linas
prev parent reply other threads:[~2006-11-29 19:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 18:05 [PATCH] ppc64_defconfig to use AUTOFS_V4 not V3 Linas Vepstas
2006-11-29 18:45 ` Olof Johansson
2006-11-29 19:32 ` Linas Vepstas [this message]
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=20061129193227.GO10879@austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=nfonteno@us.ibm.com \
--cc=olof@lixom.net \
--cc=paulus@samba.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).