On Mon, 2009-12-14 at 16:34 +1100, Stephen Rothwell wrote:
> Hi Grant,
>
> Today's linux-next build (powerpc ppc44x_defconfig) failed like this:
>
> arch/powerpc/mm/pgtable_32.c: In function 'mapin_ram':
> arch/powerpc/mm/pgtable_32.c:318: error: too many arguments to function
> 'mmu_mapin_ram'
On 14.12.2009, at 07:35, Stephen Rothwell wrote:
> Hi all,
>
> A powerpc allmodconfig fails like this:
>
> arch/powerpc/kvm/built-in.o:(.toc1+0x18): undefined reference to
> `kvm_debugfs_dir'
>
> This is because CONFIG_KVM_EXIT_TIMING is a bool while
> CONFIG_KVM_BOOK3S_64 is tristate. This c
On Fri, 2009-12-11 at 16:23 +0530, Sachin Sant wrote:
> While executing cpu_hotplug(from autotest) tests against latest
> next on a power6 box, the machine locks up. A soft reset shows
> the following trace
>
> cpu 0x0: Vector: 100 (System Reset) at [cc9333d0]
> pc: c03433d8: .
Peter Zijlstra wrote:
On Fri, 2009-12-11 at 16:23 +0530, Sachin Sant wrote:
While executing cpu_hotplug(from autotest) tests against latest
next on a power6 box, the machine locks up. A soft reset shows
the following trace
cpu 0x0: Vector: 100 (System Reset) at [cc9333d0]
pc: c00
On Mon, 2009-12-14 at 16:41 +0530, Sachin Sant wrote:
> Peter Zijlstra wrote:
> > On Fri, 2009-12-11 at 16:23 +0530, Sachin Sant wrote:
> >
> >> While executing cpu_hotplug(from autotest) tests against latest
> >> next on a power6 box, the machine locks up. A soft reset shows
> >> the following
The function name of cpumask_clear_cpu was not correct.
Reported-by: Jin Qing
Signed-off-by: Li Yang
---
This also implies that the CONFIG_HOTPLUG_CPU was never tested.
We are trying to add cpu hotplug for SMP suspend, but seeing the
following error(on 2.6.31 with context patches applied).
Any i
ence, this patch removes the DMA_INTERRUPT capability
and the associated code from the driver.
Signed-off-by: Vishnu Suresh
---
Changes with respect to v0
o. The functionality is removed instead of disabling as
per comments
o. Rebased to linux-next as of 20091214
drivers/dma/fsldm
The async_tx descriptors contains dangling pointers.
Hence, re-initialize them to NULL before use.
Signed-off-by: Vishnu Suresh
---
o. Rebased to linux-next as of 20091214
drivers/dma/fsldma.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/drivers/dma/fsldma.c b
on.
o. Rebased to linux-next as of 20091214
drivers/crypto/Kconfig |1 +
drivers/crypto/talitos.c | 397 +-
drivers/crypto/talitos.h |2 +
3 files changed, 399 insertions(+), 1 deletions(-)
diff --git a/drivers/crypto/Kconfig b/drivers/crypto/Kc
The async_tx descriptors contains dangling pointers.
Hence, re-initialize them to NULL before use.
Signed-off-by: Vishnu Suresh
---
o. Rebased to linux-next as of 20091214
drivers/crypto/talitos.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/drivers/crypto
This patch fixes the handling of VSX alignment faults in little-endian
mode (the current code assumes the processor is in big-endian mode).
The patch also makes the handlers clear the top 8 bytes of the register
when handling an 8 byte VSX load.
This is based on 2.6.32.
Signed-off-by: Neil Campb
Neil Campbell wrote:
> This patch fixes the handling of VSX alignment faults in little-endian
> mode (the current code assumes the processor is in big-endian mode).
>
> The patch also makes the handlers clear the top 8 bytes of the register
> when handling an 8 byte VSX load.
For the interested,
Hi all,
The patches were waiting for commit 2e9d546eda5888962a441da1e96bbf9
("powerpc/fsl: Make fsl_deep_sleep() usable w/ modules and non-83xx
builds") to hit Linus' tree.
Now that the commit is in, I'm resending the series with some
corrections as suggested[1] by Scott Wood.
It might be late f
This patch fixes following warnings:
ehci-fsl.c:43:5: warning: symbol 'usb_hcd_fsl_probe' was not declared. Should
it be static?
ehci-fsl.c:150:6: warning: symbol 'usb_hcd_fsl_remove' was not declared. Should
it be static?
Signed-off-by: Anton Vorontsov
---
drivers/usb/host/ehci-fsl.c |7
EHCI FSL controller preserve its state during sleep mode, so nothing
fancy needs to be done.
Though, during 'deep sleep' mode (as found in MPC831x CPUs) the
controller turns off and needs to be reinitialized upon resume.
This patch adds support for hibernation and resuming after deep sleep.
Based
On Wed, Dec 9, 2009 at 18:46:51 Grant Likely wrote:
> wrote:
> [...]
> > The following patch adds a function to get the active state of the chip
> > select of a SPI device by looking for the 'spi-cs-high' property in the
> > associated device tree node.
> > This function is used by the spi_mpc8xxx
On Sun, Dec 13, 2009 at 04:56:48PM -0800, Roland McGrath wrote:
> I can't see anything you've done to keep this use of MSR_SE in the
> user-mode register state from interfering with user_enable_single_step().
> It looks to me like you'd swallow the normal step indications.
>
Yes, it does unset MS
> Yes, it does unset MSR_SE bit in single_step_dabr_instruction()
> irrespective of whether it was previously enabled through
> user_enable_single_step(). This could be mitigated with the use of a
> separate flag which can be used to conditionally unset MSR_SE, however
> given further concerns abou
On Mon, 2009-12-14 at 21:01 +0800, Li Yang wrote:
> The function name of cpumask_clear_cpu was not correct.
>
> Reported-by: Jin Qing
> Signed-off-by: Li Yang
> ---
> This also implies that the CONFIG_HOTPLUG_CPU was never tested.
> We are trying to add cpu hotplug for SMP suspend, but seeing th
> This patch fixes the handling of VSX alignment faults in little-endian
> mode (the current code assumes the processor is in big-endian mode).
>
> The patch also makes the handlers clear the top 8 bytes of the register
> when handling an 8 byte VSX load.
>
> This is based on 2.6.32.
>
> Signed-
On Mon, 2009-12-14 at 13:19 +0100, Peter Zijlstra wrote:
> > >> cpu 0x0: Vector: 100 (System Reset) at [cc9333d0]
> > >> pc: c03433d8: .find_next_bit+0x54/0xc4
> > >> lr: c0342f10: .cpumask_next_and+0x4c/0x94
> > >> sp: cc933650
> > >>msr: 80
On machines using the Apple U4 bridge (AKA IBM CPC945) PCIe interface such
as the latest generation G5 machines x16 slot or the x16 slot of the
PowerStation, MSIs are currently broken (and will oops when enabling).
This fixes the oops and implements proper support for those. Instead of
using the P
On Mon, Dec 14, 2009 at 6:33 AM, Vishnu Suresh wrote:
> The async_tx descriptors contains dangling pointers.
> Hence, re-initialize them to NULL before use.
>
> Signed-off-by: Vishnu Suresh
> ---
> o. Rebased to linux-next as of 20091214
>
> drivers/crypto/talitos
23 matches
Mail list logo
