Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
arch/powerpc/kernel/exceptions-64s.S: Assembler messages:
arch/powerpc/kernel/exceptions-64s.S:1312: Error: attempt to move .org backwards
The last time I got this error, I needed to apply
On Mon, 2014-01-06 at 20:28 +1100, Stephen Rothwell wrote:
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
arch/powerpc/kernel/exceptions-64s.S: Assembler messages:
arch/powerpc/kernel/exceptions-64s.S:1312: Error: attempt to move
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
arch/powerpc/kernel/exceptions-64s.S: Assembler messages:
arch/powerpc/kernel/exceptions-64s.S:958: Error: attempt to move .org backwards
arch/powerpc/kernel/exceptions-64s.S:959: Error:
On Thu, Nov 21, 2013 at 02:33:34PM +1100, Anton Blanchard wrote:
Hi,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
stdin:1:0: error: -mcall-aixdesc must be big endian
Urgh, allyesconfig is building an LE kernel. Ian: do we need to
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
stdin:1:0: error: -mcall-aixdesc must be big endian
stdin:1:0: error: -mcall-aixdesc must be big endian
scripts/gcc-version.sh: line 31: printf: #: invalid number
scripts/gcc-version.sh: line
Hi,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
stdin:1:0: error: -mcall-aixdesc must be big endian
Urgh, allyesconfig is building an LE kernel. Ian: do we need to reverse
the polarity of the option, and call it CONFIG_CPU_BIG_ENDIAN?
Hi all,
Yes, I agree. The other filesystems that take an Opt_uid as well do use
current_user_ns() and not init_user_ns. They also do a uid_valid()
check and fail the mount (or fallback to GLOBAL_ROOT_UID). So I think
that would look like this:
Looks good to me. Builds and mounts as expected.
Hey Stephen,
On Wed, Aug 21, 2013 at 10:22:46AM +1000, Stephen Rothwell wrote:
On Tue, 20 Aug 2013 14:28:44 -0500 Ben Myers b...@sgi.com wrote:
I'd prefer not to break Stephen's tree two days in a row. We could just
revert
d6970d4b726c in the xfs tree for the time being as Stephen has
Hey Dwight,
On Wed, Aug 21, 2013 at 02:30:04PM +0800, Jeremy Kerr wrote:
Yes, I agree. The other filesystems that take an Opt_uid as well do use
current_user_ns() and not init_user_ns. They also do a uid_valid()
check and fail the mount (or fallback to GLOBAL_ROOT_UID). So I think
that
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
arch/powerpc/platforms/cell/spufs/inode.c: In function 'spufs_parse_options':
arch/powerpc/platforms/cell/spufs/inode.c:623:16: error: incompatible types
when assigning to type 'kuid_t' from
On Tuesday 20 August 2013, Dwight Engen wrote:
diff --git a/arch/powerpc/platforms/cell/spufs/inode.c
b/arch/powerpc/platforms/cell/spufs/inode.c
index f390042..90fb308 100644
--- a/arch/powerpc/platforms/cell/spufs/inode.c
+++ b/arch/powerpc/platforms/cell/spufs/inode.c
@@ -620,12 +620,12
On Tue, 20 Aug 2013 17:20:52 +1000
Stephen Rothwell s...@canb.auug.org.au wrote:
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
arch/powerpc/platforms/cell/spufs/inode.c: In function
'spufs_parse_options':
Hi Jeremy,
Apologies for breaking your build...
On Tue, Aug 20, 2013 at 12:07:02PM -0400, Dwight Engen wrote:
On Tue, 20 Aug 2013 17:20:52 +1000
Stephen Rothwell s...@canb.auug.org.au wrote:
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
Hi Ben,
On Tue, 20 Aug 2013 14:28:44 -0500 Ben Myers b...@sgi.com wrote:
I'd prefer not to break Stephen's tree two days in a row. We could just
revert
d6970d4b726c in the xfs tree for the time being as Stephen has done, but given
the choice would prefer the fix. Do you have a preference
Hi all,
After merging the final tree, today's linux-next build (powerpc64
allnoconfig) failed like this:
In file included from arch/powerpc/include/asm/kvm_ppc.h:33:0,
from arch/powerpc/kernel/setup_64.c:67:
arch/powerpc/include/asm/kvm_book3s.h:65:20: error: field 'pte' has
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
arch/powerpc/kernel/kgdb.c: In function 'kgdb_arch_exit':
arch/powerpc/kernel/kgdb.c:492:2: error: '__debugger_breakx_match' undeclared
(first use in this function)
Caused by commit
Stephen Rothwell s...@canb.auug.org.au wrote:
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
arch/powerpc/kernel/kgdb.c: In function 'kgdb_arch_exit':
arch/powerpc/kernel/kgdb.c:492:2: error: '__debugger_breakx_match' undeclared
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
lib/pSeries-reconfig-notifier-error-inject.c:4:34: fatal error:
asm/pSeries_reconfig.h: No such file or directory
Caused by commit f459d63e1689 (powerpc+of: Remove the pSeries_reconfig.h
On Thu, 2012-11-15 at 18:06 +1100, Stephen Rothwell wrote:
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
lib/pSeries-reconfig-notifier-error-inject.c:4:34: fatal error:
asm/pSeries_reconfig.h: No such file or directory
Caused
From: Benjamin Herrenschmidt b...@kernel.crashing.org
Date: Sat, 22 Sep 2012 07:46:40 +1000
Right, but on ppc, GFP_DMA is a nop (no separate ZONE_DMA, or rather all
of memory is ZONE_DMA). It's always been like that afaik.
We could support ISA device limited addressability using the iommu
On Sat, 2012-09-22 at 16:00 -0400, David Miller wrote:
I think I'm going to just end up restricting this driver to X86
as was originally suggested.
Probably the easiest fix indeed.
There seems to be no real consistent Kconfig protection for users
of isa_virt_to_bus() and friends.
We
On Thu, 2012-09-20 at 18:53 -0400, David Miller wrote:
From: Benjamin Herrenschmidt b...@kernel.crashing.org
Date: Fri, 21 Sep 2012 08:22:44 +1000
Hrm, that's ancient gunk, I'll have to dig. We potentially can support
ISA devices DMA'ing from an ISA bridge... but via the iommu, which means
[Just bring this to the attention of the PowerPC folks ...]
On Thu, 20 Sep 2012 16:45:58 -0400 (EDT) David Miller da...@davemloft.net
wrote:
From: Mika Westerberg mika.westerb...@linux.intel.com
Date: Thu, 20 Sep 2012 12:10:14 +0300
On Thu, Sep 20, 2012 at 05:36:22PM +1000, Stephen
I think the powerpc port is at fault here.
Part of being able to advertise ISA_DMA_API is providing isa_virt_to_bus().
Hrm, that's ancient gunk, I'll have to dig. We potentially can support
ISA devices DMA'ing from an ISA bridge... but via the iommu, which means
isa_virt_to_bus is a
Hi Dave,
On Thu, 20 Sep 2012 16:45:58 -0400 (EDT) David Miller da...@davemloft.net
wrote:
I think the powerpc port is at fault here.
Part of being able to advertise ISA_DMA_API is providing isa_virt_to_bus().
Not disagreeing, but it would be nice if this was documented somewhere
(maybe in
From: Benjamin Herrenschmidt b...@kernel.crashing.org
Date: Fri, 21 Sep 2012 08:22:44 +1000
Hrm, that's ancient gunk, I'll have to dig. We potentially can support
ISA devices DMA'ing from an ISA bridge... but via the iommu, which means
isa_virt_to_bus is a non-starter.
But then, do we
Hi all,
After merging the final tree, today's linux-next build (powerpc allyesconfig)
failed like this:
In file included from drivers/atm/fore200e.c:70:0:
drivers/atm/fore200e.h:263:3: error: redefinition of typedef 'opcode_t' with
different type
arch/powerpc/include/asm/probes.h:25:13: note:
On Thu, Sep 06, 2012 at 05:11:53PM +1000, Stephen Rothwell wrote:
Hi all,
After merging the final tree, today's linux-next build (powerpc allyesconfig)
failed like this:
In file included from drivers/atm/fore200e.c:70:0:
drivers/atm/fore200e.h:263:3: error: redefinition of typedef
On Fri, Jul 06, 2012 at 01:01:37PM +1000, Stephen Rothwell wrote:
solos-pci.c:(.text+0x1ff923c): relocation truncated to fit: R_PPC64_REL24
^
I assume at this point, we are just too large.
Yeah, but not in total. I didn't see any of these in the allyes
kernel I
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
powerpc64-linux-ld: drivers/built-in.o: In function `.gpiochip_is_requested':
(.text+0x4): sibling call optimization to `_savegpr0_29' does not allow
automatic multiple TOCs; recompile with
On Thu, Jul 05, 2012 at 06:33:45PM +1000, Stephen Rothwell wrote:
powerpc64-linux-ld: drivers/built-in.o: In function `.gpiochip_is_requested':
(.text+0x4): sibling call optimization to `_savegpr0_29' does not allow
automatic multiple TOCs; recompile with -mminimal-toc or
Hi Alan,
On Thu, 5 Jul 2012 19:13:48 +0930 Alan Modra amo...@gmail.com wrote:
On Thu, Jul 05, 2012 at 06:33:45PM +1000, Stephen Rothwell wrote:
powerpc64-linux-ld: drivers/built-in.o: In function
`.gpiochip_is_requested':
(.text+0x4): sibling call optimization to `_savegpr0_29' does not
On Fri, Jul 06, 2012 at 10:21:51AM +1000, Stephen Rothwell wrote:
which have now been fixed. So would a simple patch that puts the
_savegpr etc functions in their own section (defined how?) fix this for
us?
Ah, the kernel provides its own save/restore functions, and these get
mashed into a
Hi Alan,
On Fri, 6 Jul 2012 10:27:10 +0930 Alan Modra amo...@gmail.com wrote:
On Fri, Jul 06, 2012 at 10:21:51AM +1000, Stephen Rothwell wrote:
which have now been fixed. So would a simple patch that puts the
_savegpr etc functions in their own section (defined how?) fix this for
us?
On Thu, 2012-06-21 at 15:36 +1000, Michael Ellerman wrote:
powerpc64-linux-ld:
/src/next/net/openvswitch/vport-netdev.c:189:(.text+0x89b990):
sibling call optimization to `_restgpr0_28' does not allow automatic
multiple TOCs;
recompile with -mminimal-toc or
On Thu, 2012-06-21 at 16:24 +1000, Benjamin Herrenschmidt wrote:
On Thu, 2012-06-21 at 15:36 +1000, Michael Ellerman wrote:
powerpc64-linux-ld:
/src/next/net/openvswitch/vport-netdev.c:189:(.text+0x89b990):
sibling call optimization to `_restgpr0_28' does not allow
automatic
On Thu, Jun 21, 2012 at 03:36:01PM +1000, Michael Ellerman wrote:
On Wed, 2012-06-20 at 17:50 +1000, Stephen Rothwell wrote:
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
powerpc64-linux-ld: arch/powerpc/net/built-in.o: In
On Thu, 2012-06-21 at 17:07 +1000, Michael Ellerman wrote:
On Thu, 2012-06-21 at 16:24 +1000, Benjamin Herrenschmidt wrote:
On Thu, 2012-06-21 at 15:36 +1000, Michael Ellerman wrote:
powerpc64-linux-ld:
/src/next/net/openvswitch/vport-netdev.c:189:(.text+0x89b990):
On Thu, Jun 21, 2012 at 05:38:27PM +1000, Michael Ellerman wrote:
On Thu, 2012-06-21 at 17:07 +1000, Michael Ellerman wrote:
On Thu, 2012-06-21 at 16:24 +1000, Benjamin Herrenschmidt wrote:
On Thu, 2012-06-21 at 15:36 +1000, Michael Ellerman wrote:
powerpc64-linux-ld:
On Thu, Jun 21, 2012 at 08:18:39PM +0930, Alan Modra wrote:
Linker bug. That's not a sibling call, but a normal function return
via an out-of-line register restore function.
I couldn't see how this might be occurring, then I remembered the
kernel has this horrible practise of using ld -r to
On Thu, 2012-06-21 at 21:13 +0930, Alan Modra wrote:
On Thu, Jun 21, 2012 at 08:18:39PM +0930, Alan Modra wrote:
Linker bug. That's not a sibling call, but a normal function return
via an out-of-line register restore function.
I couldn't see how this might be occurring, then I remembered
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
powerpc64-linux-ld: arch/powerpc/net/built-in.o: In function
`bpf_slow_path_word':
(.text+0x90): sibling call optimization to `skb_copy_bits' does not allow
automatic multiple TOCs;
On Wed, 2012-06-20 at 17:50 +1000, Stephen Rothwell wrote:
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
I hate our ABI is a good answer ? :-)
I'll see what I can do tomorrow. Poke me when I'm in the office.
Cheers,
Ben.
On Wed, 2012-06-20 at 17:50 +1000, Stephen Rothwell wrote:
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
powerpc64-linux-ld: arch/powerpc/net/built-in.o: In function
`bpf_slow_path_word':
(.text+0x90): sibling call optimization
On Mon, 2012-02-27 at 17:37 +1100, Stephen Rothwell wrote:
pci_add_resource_offset(resources, res,
- (resource_size_t) hose-io_base_virt - _IO_BASE);
+ (resource_size_t)(unsigned long)hose-io_base_virt -
_IO_BASE);
We have to be careful
On Mon, 2012-02-27 at 20:19 +1100, Benjamin Herrenschmidt wrote:
On Mon, 2012-02-27 at 17:37 +1100, Stephen Rothwell wrote:
pci_add_resource_offset(resources, res,
- (resource_size_t) hose-io_base_virt - _IO_BASE);
+
Hi all,
After merging the final tree, today's linux-next build (powerpc
ppc44x_defconfig) failed like this:
arch/powerpc/kernel/pci-common.c: In function 'pcibios_setup_phb_resources':
arch/powerpc/kernel/pci-common.c:1520:4: error: cast from pointer to integer of
different size
Hi Andrew,
After merging the final tree, today's linux-next build (powerpc
allnoconfig) failed like this:
In file included from include/linux/posix_types.h:47:0,
from include/linux/types.h:17,
from include/linux/page-flags.h:8,
from
On Fri, 2012-02-17 at 16:30 +1100, Stephen Rothwell wrote:
Hi Andrew,
After merging the final tree, today's linux-next build (powerpc
allnoconfig) failed like this:
In file included from include/linux/posix_types.h:47:0,
from include/linux/types.h:17,
On 01/20/2012 12:51 PM, Stephen Rothwell wrote:
Hi all,
After merging the final tree, today's linux-next build (powerpc
allmodconfig) failed like this:
arch/powerpc/platforms/pseries/processor_idle.c:35:6: error: redefinition of
'update_smt_snooze_delay'
Hi all,
After merging the final tree, today's linux-next build (powerpc
allmodconfig) failed like this:
arch/powerpc/platforms/pseries/processor_idle.c:35:6: error: redefinition of
'update_smt_snooze_delay'
arch/powerpc/include/asm/system.h:230:20: note: previous definition of
On Wed, Dec 28, 2011 at 09:32:14PM +1100, Benjamin Herrenschmidt wrote:
On Wed, 2011-12-28 at 19:49 +1100, Stephen Rothwell wrote:
Hi ,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
kernel/built-in.o: In function
On Mon, Jan 2, 2012 at 1:25 AM, Grant Likely grant.lik...@secretlab.ca wrote:
On Wed, Dec 28, 2011 at 09:32:14PM +1100, Benjamin Herrenschmidt wrote:
On Wed, 2011-12-28 at 19:49 +1100, Stephen Rothwell wrote:
Hi ,
After merging the final tree, today's linux-next build (powerpc
Hi ,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
kernel/built-in.o: In function `irq_dispose_mapping':
(.opd+0x159f0): multiple definition of `irq_dispose_mapping'
arch/powerpc/kernel/built-in.o:(.opd+0x960): first defined here
On Wed, 2011-12-28 at 19:49 +1100, Stephen Rothwell wrote:
Hi ,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
kernel/built-in.o: In function `irq_dispose_mapping':
(.opd+0x159f0): multiple definition of `irq_dispose_mapping'
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/tty/ehv_bytechan.c: In function 'udbg_init_ehv_bc':
drivers/tty/ehv_bytechan.c:230:18: error: 'MSR_GS' undeclared (first use in
this function)
drivers/tty/ehv_bytechan.c: In function
On Aug 25, 2011, at 9:08 AM, Greg KH g...@kroah.com wrote:
On Thu, Aug 25, 2011 at 04:18:43PM +1000, Stephen Rothwell wrote:
Thanks for the report.
Timur, care to send a fixup patch for this so this gets resolved?
Yes, I will do it ASAP, probably within the next two hours.
On Thu, Aug 25, 2011 at 04:18:43PM +1000, Stephen Rothwell wrote:
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/tty/ehv_bytechan.c: In function 'udbg_init_ehv_bc':
drivers/tty/ehv_bytechan.c:230:18: error: 'MSR_GS'
Greg KH wrote:
MSR_GS is defined in arch/powerpc/include/asm/reg_booke.h which is
included by arch/powerpc/include/asm/reg.h but only when defined
(CONFIG_BOOKE) || defined(CONFIG_40x).
Thanks for the report.
Timur, care to send a fixup patch for this so this gets resolved?
Is there
Hi Timur,
On Thu, 25 Aug 2011 10:22:05 -0500 Timur Tabi ti...@freescale.com wrote:
Is there some trick to building allyesconfig on PowerPC? When I do try that,
I
get all sorts of weird build errors, and it dies long before it gets to my
driver. I get stuff like:
LD
Hi,
On Thu, Aug 25, 2011 at 11:51 AM, Stephen Rothwell s...@canb.auug.org.au
wrote:
Hi Timur,
On Thu, 25 Aug 2011 10:22:05 -0500 Timur Tabi ti...@freescale.com wrote:
Is there some trick to building allyesconfig on PowerPC? When I do try
that, I
get all sorts of weird build errors, and
Hi Arnaud,
On Thu, 25 Aug 2011 12:09:20 -0400 Arnaud Lacombe lacom...@gmail.com wrote:
If you could provide an exhaustive list of them, I'd be interested. Do
you account/reference them in the report you make on each new -next
tree ?
I don't refer to them at all :-(
If you are not just
Hi all,
After merging the final tree, today's linux-next build (powerpc
allysconfig) failed like this:
arch/powerpc/kernel/exceptions-64s.S: Assembler messages:
arch/powerpc/kernel/exceptions-64s.S:1151: Error: attempt to move .org backwards
arch/powerpc/kernel/exceptions-64s.S:1160: Error:
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/tty/hvc/hvsi.c:701:12: error: conflicting types for 'hvsi_put_chars'
arch/powerpc/include/asm/hvsi.h:92:12: note: previous declaration of
'hvsi_put_chars' was here
On Thu, 2011-06-30 at 16:36 +1000, Stephen Rothwell wrote:
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/tty/hvc/hvsi.c:701:12: error: conflicting types for 'hvsi_put_chars'
arch/powerpc/include/asm/hvsi.h:92:12: note:
On Fri, 17 Jun 2011 15:38:09 +1000
Stephen Rothwell s...@canb.auug.org.au wrote:
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
mm/page_cgroup.c: In function 'page_cgroup_init':
mm/page_cgroup.c:309:13: error: 'pg_data_t' has no
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
mm/page_cgroup.c: In function 'page_cgroup_init':
mm/page_cgroup.c:309:13: error: 'pg_data_t' has no member named 'node_end_pfn'
Caused by commit 37573e8c7182 (memcg: fix init_page_cgroup nid
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
arch/powerpc/mm/mmu_context_hash64.c: In function 'init_new_context':
arch/powerpc/mm/mmu_context_hash64.c:282: error: 'NO_CONTEXT' undeclared (first
use in this function)
Presumably caused
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/mtd/ubi/io.c: In function 'ubi_dbg_check_write':
drivers/mtd/ubi/io.c:1348: error: 'PAGE_KERNEL' undeclared (first use in this
function)
drivers/mtd/ubi/io.c: In function
On Wed, 2011-03-16 at 09:22 +0200, Artem Bityutskiy wrote:
On Wed, 2011-03-16 at 17:50 +1100, ext Stephen Rothwell wrote:
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/mtd/ubi/io.c: In function 'ubi_dbg_check_write':
On Wed, 2011-03-16 at 17:50 +1100, ext Stephen Rothwell wrote:
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/mtd/ubi/io.c: In function 'ubi_dbg_check_write':
drivers/mtd/ubi/io.c:1348: error: 'PAGE_KERNEL' undeclared (first
On Wed, 2011-03-16 at 21:15 +1100, Benjamin Herrenschmidt wrote:
On Wed, 2011-03-16 at 09:22 +0200, Artem Bityutskiy wrote:
On Wed, 2011-03-16 at 17:50 +1100, ext Stephen Rothwell wrote:
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed
On Wed, 2011-03-16 at 17:50 +1100, Stephen Rothwell wrote:
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/mtd/ubi/io.c: In function 'ubi_dbg_check_write':
drivers/mtd/ubi/io.c:1348: error: 'PAGE_KERNEL' undeclared (first use in this
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/gpio/langwell_gpio.c: In function 'lnw_irq_handler':
drivers/gpio/langwell_gpio.c:210: error: 'struct irq_desc' has no member named
'chip'
drivers/gpio/langwell_gpio.c:211: error:
On Fri, Mar 11, 2011 at 08:12:38AM +0100, Jens Axboe wrote:
On 2011-03-11 07:58, Stephen Rothwell wrote:
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/char/tpm/tpm_tis.c:96: warning: 'is_itpm' defined but not used
On Mon, 2011-03-14 at 20:38 +1100, Stephen Rothwell wrote:
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/gpio/langwell_gpio.c: In function 'lnw_irq_handler':
drivers/gpio/langwell_gpio.c:210: error: 'struct irq_desc' has no
From: Benjamin Herrenschmidt b...@kernel.crashing.org
Date: Tue, 15 Mar 2011 07:37:54 +1100
On Mon, 2011-03-14 at 20:38 +1100, Stephen Rothwell wrote:
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/gpio/langwell_gpio.c: In
On Mon, 14 Mar 2011, David Miller wrote:
From: Benjamin Herrenschmidt b...@kernel.crashing.org
Date: Tue, 15 Mar 2011 07:37:54 +1100
On Mon, 2011-03-14 at 20:38 +1100, Stephen Rothwell wrote:
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig)
On Tue, Mar 15, 2011 at 07:37:54AM +1100, Benjamin Herrenschmidt wrote:
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/gpio/langwell_gpio.c: In function 'lnw_irq_handler':
drivers/gpio/langwell_gpio.c:210: error:
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
arch/powerpc/kernel/exceptions-64s.S: Assembler messages:
arch/powerpc/kernel/exceptions-64s.S:989: Error: attempt to move .org backwards
arch/powerpc/kernel/exceptions-64s.S:999: Error:
On Fri, Dec 03, 2010 at 04:59:58PM +1100, Benjamin Herrenschmidt wrote:
On Fri, 2010-12-03 at 16:32 +1100, Stephen Rothwell wrote:
After merging the tree, today's linux-next build (powerpc allmodconfig)
failed like this:
arch/powerpc/lib/hweight_64.S: Assembler messages:
Hi all,
After merging the tree, today's linux-next build (powerpc allmodconfig)
failed like this:
arch/powerpc/lib/hweight_64.S: Assembler messages:
arch/powerpc/lib/hweight_64.S:52: Error: Unrecognized opcode: `popcntw'
arch/powerpc/lib/hweight_64.S:77: Error: Unrecognized opcode: `popcntw'
On Fri, 2010-12-03 at 16:32 +1100, Stephen Rothwell wrote:
After merging the tree, today's linux-next build (powerpc allmodconfig)
failed like this:
arch/powerpc/lib/hweight_64.S: Assembler messages:
arch/powerpc/lib/hweight_64.S:52: Error: Unrecognized opcode: `popcntw'
On Fri, 03 Dec 2010 16:59:58 +1100 Benjamin Herrenschmidt
b...@kernel.crashing.org wrote:
This toolchain is a bit ancient I suppose... Anton, do you reckon we
should use .long based macros for these for the time being or just
require a newer binutils ?
The currently documented minimum
Hi Ben,
On Fri, 3 Sep 2010 13:24:10 +1000 Stephen Rothwell s...@canb.auug.org.au
wrote:
After merging the final tree, today's linux-next build
(powerpc64 allnoconfig) failed like this:
arch/powerpc/kernel/built-in.o: In function `.sys_call_table':
(.text+0x8d48): undefined reference to
Hi all,
After merging the final tree, today's linux-next build
(powerpc64 allnoconfig) failed like this:
arch/powerpc/kernel/built-in.o: In function `.sys_call_table':
(.text+0x8d48): undefined reference to `.compat_sys_recv'
Caused by commit 86250b9d12caa1a3dee12a7cf638b7dd70eaadb6 (powerpc:
On Fri, 2010-07-16 at 17:19 +1000, Stephen Rothwell wrote:
Hi all,
After merging the final tree, today's linux-next build (powerpc
allmodconfig) failed like this:
ERROR: of_i8042_kbd_irq [drivers/input/serio/i8042.ko] undefined!
ERROR: of_i8042_aux_irq [drivers/input/serio/i8042.ko]
Hi all,
After merging the final tree, today's linux-next build (powerpc
allmodconfig) failed like this:
ERROR: of_i8042_kbd_irq [drivers/input/serio/i8042.ko] undefined!
ERROR: of_i8042_aux_irq [drivers/input/serio/i8042.ko] undefined!
Presumably missing EXPORT_SYMBOLs ..
--
Cheers,
Stephen
On Fri, 2010-05-28 at 15:08 +1000, Stephen Rothwell wrote:
Hi Steven,
After merging the final tree, today's linux-next build (powerpc allyesconfig)
failed like this:
arch/powerpc/platforms/pseries/hvCall_inst.c: In function 'hcall_inst_init':
Hi Steven,
After merging the final tree, today's linux-next build (powerpc allyesconfig)
failed like this:
arch/powerpc/platforms/pseries/hvCall_inst.c: In function 'hcall_inst_init':
arch/powerpc/platforms/pseries/hvCall_inst.c:143: warning: passing argument 1
of 'register_trace_hcall_entry'
90 matches
Mail list logo
