mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Maurice Volaski <mvolaski@aecom.yu.edu>
To: Michael Hanselmann <hansmi@gentoo.org>
Cc: gentoo-ppc-dev@lists.gentoo.org, linuxppc64-dev@ozlabs.org,
	linux-kernel@vger.kernel.org
Subject: Re: [gentoo-ppc-dev] CONFIG_THERM_PM72 is missing from .config from recent kernels (2.6.10, 2.6.11)
Date: Sat, 29 Jan 2005 18:41:19 -0500	[thread overview]
Message-ID: <a0620073cbe21c8047634@[129.98.90.227]> (raw)
In-Reply-To: <20050129103057.GA27803@hansmi.ch>

>Hello Maurice
>
>>  It's missing from .config in at least a few releases of recent
>>  kernels (2.6.10, 2.6.11).
>
>Definitly not true, at least for ppc32.

Note that..

1) I looked only at official kernel source code
and
2) I looked only at a few releases, not every patchset.
and
3) I looked only at the resulting .config file after preparing it 
with make menuconfig.

>Linux g5 2.6.10-gentoo-r6-g5 #6 SMP Wed Jan 26 23:05:05 CET 2005 ppc
>PPC970, altivec supported PowerMac7,2 GNU/Linux

 From what I can tell, the .config file is built up from different 
files. I just looked at gentoo-dev-sources for this version and it 
is, in fact, present for ppc64 in
/usr/src/linux-2.6.10-gentoo-r6/arch/ppc64/defconfig

That suggests the mechanism that generates the .config files is not 
working right under certain circumstances related to the 64bit G5.
-- 

Maurice Volaski, mvolaski@aecom.yu.edu
Computing Support, Rose F. Kennedy Center
Albert Einstein College of Medicine of Yeshiva University

       reply	other threads:[~2005-01-29 23:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a06200736be209a45bd65@[129.98.90.227]>
     [not found] ` <20050129103057.GA27803@hansmi.ch>
2005-01-29 23:41   ` Maurice Volaski [this message]
2005-01-30 23:21     ` Benjamin Herrenschmidt

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='a0620073cbe21c8047634@[129.98.90.227]' \
    --to=mvolaski@aecom.yu.edu \
    --cc=gentoo-ppc-dev@lists.gentoo.org \
    --cc=hansmi@gentoo.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc64-dev@ozlabs.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

all inboxes | Powered by JetHome®