arm:allmodconfig, arm:omap2plus_defconfig:
FATAL ERROR: Unable to parse input tree
make[1]: *** [arch/arm/boot/dts/omap5-uevm.dtb] Error 1
make: *** [dtbs] Error 2
Culprit is 'ARM: dts: Fix WLAN regression on omap5-uevm', which uses defines
which are only available in later kernels.
Guenter
--
On Sun, Dec 06, 2015 at 07:17:51AM -0800, Guenter Roeck wrote:
> arm:allmodconfig, arm:omap2plus_defconfig:
>
> FATAL ERROR: Unable to parse input tree
> make[1]: *** [arch/arm/boot/dts/omap5-uevm.dtb] Error 1
> make: *** [dtbs] Error 2
>
> Culprit is 'ARM: dts: Fix WLAN regression on omap5-uevm'
* Guenter Roeck [151206 07:18]:
> arm:allmodconfig, arm:omap2plus_defconfig:
>
> FATAL ERROR: Unable to parse input tree
> make[1]: *** [arch/arm/boot/dts/omap5-uevm.dtb] Error 1
> make: *** [dtbs] Error 2
>
> Culprit is 'ARM: dts: Fix WLAN regression on omap5-uevm', which uses defines
> which a
* Greg Kroah-Hartman [151206 08:25]:
> On Sun, Dec 06, 2015 at 07:17:51AM -0800, Guenter Roeck wrote:
> > arm:allmodconfig, arm:omap2plus_defconfig:
> >
> > FATAL ERROR: Unable to parse input tree
> > make[1]: *** [arch/arm/boot/dts/omap5-uevm.dtb] Error 1
> > make: *** [dtbs] Error 2
> >
> > Cu
From: Stefan Wahren
Date: Fri, 4 Dec 2015 16:29:10 +0100
> In case of a tx queue timeout every transmit is blocked until the
> QCA7000 resets himself and triggers a sync which makes the driver
> flushs the tx ring. So avoid this blocking situation by triggering
> the sync immediately after the t
On 06.12.2015 08:29, Oded Gabbay wrote:
On Sat, Dec 5, 2015 at 12:23 PM, Christian König
wrote:
Patch #1 & #2 are Reviewed-by: Christian König
For patch #3:
Couldn't we just in a loop go over all the dw in the IB and swap them after
writing them? That would simplify the patch massively.
I g
On Sun, Dec 6, 2015 at 8:45 PM, Christian König wrote:
> On 06.12.2015 08:29, Oded Gabbay wrote:
>>
>> On Sat, Dec 5, 2015 at 12:23 PM, Christian König
>> wrote:
>>>
>>> Patch #1 & #2 are Reviewed-by: Christian König
>>>
>>> For patch #3:
>>>
>>> Couldn't we just in a loop go over all the dw in
On 06.12.2015 20:00, Oded Gabbay wrote:
On Sun, Dec 6, 2015 at 8:45 PM, Christian König wrote:
On 06.12.2015 08:29, Oded Gabbay wrote:
On Sat, Dec 5, 2015 at 12:23 PM, Christian König
wrote:
Patch #1 & #2 are Reviewed-by: Christian König
For patch #3:
Couldn't we just in a loop go over al
OK, I'll take a look
Oded
> Yeah, CIK support in amdgpu was only for debugging and bringup. But since
> it's only shared code you touch when it works with CIK it should work with VI
> as well and that's rather interesting to us. Regards, Christian.
--
To unsubscribe from this list: send the
Hi Chris,
On Fri, Dec 04, 2015 at 04:05:26PM +, Chris Wilson wrote:
> A long time ago (before 3.14) we relied on a permanent pinning of the
> ifbdev to lock the fb in place inside the GGTT. However, the
> introduction of stealing the BIOS framebuffer and reusing its address in
> the GGTT for t
On Mon, 2015-11-30 at 23:22 +0800, Huacai Chen wrote:
> In history, __arch_local_irq_restore() is only used by SMTC. However,
> SMTC support has been removed since 3.16, this patch remove the unused
> function.
>
> Cc:
> Signed-off-by: Huacai Chen
[...]
If this is only a clean-up, then it is no
The OPAL event calls return a mask of events that are active in big
endian format. This is checked when unmasking the events in the
irqchip by comparison with a cached value. The cached value was stored
in big endian format but should've been converted to CPU endian
first. This bug leads to OPAL ev
Free skb for received frames with a wrong checksum. This can happen
pretty rapidly, exhausting all memory.
This fixes a memleak (detected with kmemleak). Originally found while
using monitor mode, but it also appears during managed mode (once the
link is up).
Cc: stable@vger.kernel.org
Signed-off
On Sun, Dec 06, 2015 at 09:56:34PM +0100, Stefan Priebe wrote:
> Hi Herbert,
>
> i think i found the issue in 4.1 with netlink. Somebody made a
> mistake while backporting or cherry-picking your patch "netlink: Fix
> autobind race condition that leads to zero port ID" to 4.1.
>
> It misses a goto
On 12/06/2015 06:07 PM, Peter Wu wrote:
Free skb for received frames with a wrong checksum. This can happen
pretty rapidly, exhausting all memory.
This fixes a memleak (detected with kmemleak). Originally found while
using monitor mode, but it also appears during managed mode (once the
link is u
Hi Herbert,
Am 07.12.2015 um 02:20 schrieb Herbert Xu:
> On Sun, Dec 06, 2015 at 09:56:34PM +0100, Stefan Priebe wrote:
>> Hi Herbert,
>>
>> i think i found the issue in 4.1 with netlink. Somebody made a
>> mistake while backporting or cherry-picking your patch "netlink: Fix
>> autobind race condi
16 matches
Mail list logo