All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Please pull from 'for_paulus' branch
Date: Thu, 17 May 2007 08:00:42 -0500	[thread overview]
Message-ID: <5F8D37B3-5A2B-49D8-A7C2-615436EA66D3@kernel.crashing.org> (raw)
In-Reply-To: <17996.13115.456275.413478@cargo.ozlabs.ibm.com>


On May 17, 2007, at 5:49 AM, Paul Mackerras wrote:

> Kumar Gala writes:
>
>> diff --git a/arch/ppc/mm/hashtable.S b/arch/ppc/mm/htashtable.S
>> index e756942..fc30b6f 100644
>> --- a/arch/ppc/mm/hashtable.S
>> +++ b/arch/ppc/mm/hashtable.S
>
>> @@ -461,9 +465,15 @@ found_slot:
>>  	sync		/* make sure pte updates get to memory */
>>  	blr
>>
>> -	.comm	next_slot,4
>> -	.comm	primary_pteg_full,4
>> -	.comm	htab_hash_searches,4
>> +	.section .bss
>> +	.align	2
>> +next_slot:
>> +	.space	4
>> +primary_pteg_full:
>> +	.space	4
>> +htab_hash_searches:
>> +	.space	4
>> +	.previous
>
> I get this on an ARCH=ppc prep build:
>
> arch/ppc/kernel/built-in.o: In function `__main':
> arch/ppc/kernel/entry.S:(.text+0x2eda): undefined reference to  
> `htab_hash_searches'
> arch/ppc/kernel/entry.S:(.text+0x2ede): undefined reference to  
> `htab_hash_searches'
> arch/ppc/kernel/entry.S:(.text+0x2ee2): undefined reference to  
> `primary_pteg_full'
> arch/ppc/kernel/entry.S:(.text+0x2ee6): undefined reference to
> `primary_pteg_full'
>
> (The references are actually in arch/ppc/kernel/ppc_htab.c.)
>
> I guess I'll cherry-pick the other commits from your tree, since I'm
> making a string for Linus, unless you have a better suggestion.

Sorry for the headache, I thought I had built an ARCH=ppc kernel.   
This is now fixed in my tree so if you haven't pulled it you'll get  
the fix.

Also, added a ppc_ksysm.c fix to remove a duplicate export symbol.

- k

  parent reply	other threads:[~2007-05-17 13:00 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-15 22:20 Please pull from 'for_paulus' branch Kumar Gala
2007-05-17 10:49 ` Paul Mackerras
2007-05-17 12:05   ` Segher Boessenkool
2007-05-17 12:58     ` Kumar Gala
2007-05-17 13:00   ` Kumar Gala [this message]
2007-05-18  6:15     ` Paul Mackerras
2007-05-18 16:51       ` Kumar Gala
  -- strict thread matches above, loose matches on Subject: below --
2007-07-23 21:01 Kumar Gala
2007-07-24  2:56 ` Kumar Gala
2007-07-25  6:43 ` Zang Roy-r61911
2007-07-10  5:42 Kumar Gala
2007-06-29  5:24 Kumar Gala
2007-06-29  6:26 ` Paul Mackerras
2007-06-29  7:04   ` Kumar Gala
2007-06-29  9:15   ` Segher Boessenkool
2007-06-29  9:31     ` Paul Mackerras
2007-06-29  9:51       ` Segher Boessenkool
2007-06-29 13:45   ` Arnd Bergmann
2007-06-29 14:44     ` Kumar Gala
2007-06-29 16:05       ` Arnd Bergmann
2007-06-29 16:09         ` Kumar Gala
2007-06-29 16:10         ` Kumar Gala
2007-06-29 15:22   ` Andreas Schwab
2007-06-30  6:57     ` Paul Mackerras
2007-06-30  8:10       ` Andreas Schwab
2007-06-30  8:14         ` Paul Mackerras
2007-06-30  8:49           ` Andreas Schwab
2007-06-30 10:57       ` Alan Modra
2007-02-17 22:38 Kumar Gala
2007-02-17 22:44 ` Kumar Gala
2007-02-13 22:16 Kumar Gala
2007-02-08 21:50 Kumar Gala
2007-02-08 21:52 ` Please pull from 'for_paulus' branch Kumar Gala
2007-02-07  7:51 Kumar Gala
2006-12-08  8:51 Kumar Gala

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=5F8D37B3-5A2B-49D8-A7C2-615436EA66D3@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.