dtc: Make many functions 'static'

2008-08-03 Thread David Gibson
This patch marks various functions not shared between c files 'static', as they should be. There are a couple of functions in dtc, and many in the testsuite. This is *almost* enough to enable the -Wmissing-prototypes warning. It's not quite enough, because there's a mess of junk in the flex gener

Re: nfsd, v4: oops in find_acceptable_alias, ppc32 Linux, post-2.6.27-rc1

2008-08-03 Thread Paul Collins
Neil Brown <[EMAIL PROTECTED]> writes: > bctrl appears to be the indirect-function-call opcode. There are > three of them one each for > ->fh_to_dentry > acceptable > ->fh_to_parent > > 0xa8 is 'acceptable'. > > In the first traceback, the crash was a call from very early in > find_accepta

[git pull] Please pull powerpc.git merge branch

2008-08-03 Thread Paul Mackerras
Linus, Please pull from the 'merge' branch of git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git merge The main thing there is that we have moved the powerpc include files from include/asm-powerpc to arch/powerpc/include/asm. There is also a commit from Kumar Gala that removes cod

Re: nfsd, v4: oops in find_acceptable_alias, ppc32 Linux, post-2.6.27-rc1

2008-08-03 Thread Neil Brown
On Monday August 4, [EMAIL PROTECTED] wrote: > Neil Brown <[EMAIL PROTECTED]> writes: > > > > What filesystem is being exported here? > > Boring old ext3 (on LVM, on dm-crypt). Good. That makes it easier. > > > Can you get an assembly version of exportfs_decode_fh, so we can check > > what is

to schedule() or not to schedule() ?

2008-08-03 Thread Kevin Diggs
Hi, I have the following near the top of my cpufreq driver target routine: while(test_and_set_bit(cf750gxmCfgChangeBit,&cf750gxvStateBits)) { /* * Someone mucking with our cfg? (I hope it is ok to call * schedule() here! - truth is I have no idea what I am doin

Re: [PATCH v2] powerpc: move include files to arch/powerpc/include/asm

2008-08-03 Thread Stephen Rothwell
On Sun, 3 Aug 2008 09:58:14 -0500 Kumar Gala <[EMAIL PROTECTED]> wrote: > > Paul, what's the plan for this change? If this is something that will > go in so can we get a tree with it so we can base other patches on it > (like the PPC_MERGE cleanup)? It looks like Linus is happy to take these

Re: [PATCH v2] powerpc: move include files to arch/powerpc/include/asm

2008-08-03 Thread Stephen Rothwell
On Fri, 1 Aug 2008 15:20:30 +1000 Stephen Rothwell <[EMAIL PROTECTED]> wrote: > > This patch can be applied with "git am" - the full patch is way to bug ^^^ Freudian slip :-) -- Cheers, Stephen Rothwell[EMAIL

Re: [PATCH v2] powerpc: move include files to arch/powerpc/include/asm

2008-08-03 Thread Kumar Gala
On Aug 1, 2008, at 12:20 AM, Stephen Rothwell wrote: from include/asm-powerpc. This is the result of a mkdir arch/powerpc/include/asm git mv include/asm-powerpc/* arch/powerpc/include/asm Followed by a few documentation/comment fixups and a couple of places where was being used explicitly.

Re: [PATCH 8/8] powerpc: last bits to support kdump on ppc32

2008-08-03 Thread Michael Ellerman
On Fri, 2008-08-01 at 18:14 +0400, Anton Vorontsov wrote: > From: Dale Farnsworth <[EMAIL PROTECTED]> > > Wire up the trampoline code for ppc32 to relay exceptions from the > vectors at address 0 to vectors at address 32MB, and modify Kconfig > to enable Kdump support for all powerpcs (except Book

Re: nfsd, v4: oops in find_acceptable_alias, ppc32 Linux, post-2.6.27-rc1

2008-08-03 Thread Paul Collins
Neil Brown <[EMAIL PROTECTED]> writes: > On Sunday August 3, [EMAIL PROTECTED] wrote: >> >> I can trigger it reliably with a 2.6.26 client. I've also triggered it >> with 496d6c32d4d057cb44272d9bd587ff97d023ee92 reverted on the server. >> >> It's harder to trigger with 2.6.27-rc1+ but I managed

Re: nfsd, v4: oops in find_acceptable_alias, ppc32 Linux, post-2.6.27-rc1

2008-08-03 Thread Neil Brown
On Sunday August 3, [EMAIL PROTECTED] wrote: > > I can trigger it reliably with a 2.6.26 client. I've also triggered it > with 496d6c32d4d057cb44272d9bd587ff97d023ee92 reverted on the server. > > It's harder to trigger with 2.6.27-rc1+ but I managed to get an Oops > on the fourth build after thr