Hi all,
Please do not add v5.4 material to your linux-next included branches
until after v5.3-rc1 has been released.
Changes since 20190710:
The block tree gained build failures due to an interaction with the
f2fs and xfs trees for which I applied merge fix patches.
Non-merge commits (relative
Hi all,
Changes since 20180710:
News: This release fails my simple PowerPC qemu boot without kvm ...
The driver-core tree gained conflicts against the iommu tree.
The scsi-mkp tree gained a conflict against Linus' tree.
Non-merge commits (relative to Linus' tree): 5214
5338 files changed,
Hi all,
Changes since 20180710:
News: This release fails my simple PowerPC qemu boot without kvm ...
The driver-core tree gained conflicts against the iommu tree.
The scsi-mkp tree gained a conflict against Linus' tree.
Non-merge commits (relative to Linus' tree): 5214
5338 files changed,
Hi all,
Please do not add any v4.14 material to you linux-next included branches
until after v4.13-rc1 has been released.
Changes since 20170710:
The mips tree gained a conflict against Linus' tree.
The vfs tree lost its build failures but gained another for which I
applied a fix patch.
The
Hi all,
Please do not add any v4.14 material to you linux-next included branches
until after v4.13-rc1 has been released.
Changes since 20170710:
The mips tree gained a conflict against Linus' tree.
The vfs tree lost its build failures but gained another for which I
applied a fix patch.
The
Hi all,
Changes since 20160708:
The arm64 tree gained a conflict against Linus' tree.
The pm tree gained a build failure so I used the version from
next-20160708.
The wireless-drivers-next tree gained a conflict against the net-next
tree.
The drm tree gained a conflict against the jc_docs
Hi all,
Changes since 20160708:
The arm64 tree gained a conflict against Linus' tree.
The pm tree gained a build failure so I used the version from
next-20160708.
The wireless-drivers-next tree gained a conflict against the net-next
tree.
The drm tree gained a conflict against the jc_docs
On Sat, Jul 12, 2014 at 6:26 PM, Nick Krause wrote:
> On Fri, Jul 11, 2014 at 3:18 AM, Stephen Rothwell
> wrote:
>> Hi all,
>>
>> Changes since 20140710:
>>
>> My fixes tree contains:
>> powerpc: Disable RELOCATABLE for COMPILE_TEST with PPC64
>>
>> The tty.current tree gained a build
On Fri, Jul 11, 2014 at 3:18 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20140710:
>
> My fixes tree contains:
> powerpc: Disable RELOCATABLE for COMPILE_TEST with PPC64
>
> The tty.current tree gained a build failure so I used the version from
> next-20140710.
>
> The irqchip
On Fri, Jul 11, 2014 at 3:18 AM, Stephen Rothwell s...@canb.auug.org.au wrote:
Hi all,
Changes since 20140710:
My fixes tree contains:
powerpc: Disable RELOCATABLE for COMPILE_TEST with PPC64
The tty.current tree gained a build failure so I used the version from
next-20140710.
On Sat, Jul 12, 2014 at 6:26 PM, Nick Krause xerofo...@gmail.com wrote:
On Fri, Jul 11, 2014 at 3:18 AM, Stephen Rothwell s...@canb.auug.org.au
wrote:
Hi all,
Changes since 20140710:
My fixes tree contains:
powerpc: Disable RELOCATABLE for COMPILE_TEST with PPC64
The tty.current
On 07/11/14 00:18, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20140710:
>
on x86_64:
CONFIG_DVB_AV7110=y
CONFIG_INPUT_EVDEV=m
drivers/built-in.o: In function `av7110_emit_keyup':
av7110_ir.c:(.text+0x76b608): undefined reference to `input_event'
av7110_ir.c:(.text+0x76b61a):
Hi all,
Changes since 20140710:
My fixes tree contains:
powerpc: Disable RELOCATABLE for COMPILE_TEST with PPC64
The tty.current tree gained a build failure so I used the version from
next-20140710.
The irqchip tree gained a conflict against the arm64 tree.
The staging tree lost its
Hi all,
Changes since 20140710:
My fixes tree contains:
powerpc: Disable RELOCATABLE for COMPILE_TEST with PPC64
The tty.current tree gained a build failure so I used the version from
next-20140710.
The irqchip tree gained a conflict against the arm64 tree.
The staging tree lost its
On 07/11/14 00:18, Stephen Rothwell wrote:
Hi all,
Changes since 20140710:
on x86_64:
CONFIG_DVB_AV7110=y
CONFIG_INPUT_EVDEV=m
drivers/built-in.o: In function `av7110_emit_keyup':
av7110_ir.c:(.text+0x76b608): undefined reference to `input_event'
av7110_ir.c:(.text+0x76b61a): undefined
On Fri, Jul 12, 2013 at 2:47 AM, Randy Dunlap wrote:
> On 07/10/13 21:17, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20130710:
>>
>
>
> on x86_64:
>
> # CONFIG_USB_GADGET is not set
>
> ERROR: "usb_gadget_map_request" [drivers/usb/chipidea/ci_hdrc.ko] undefined!
> ERROR:
; linux-kernel@vger.kernel.org; Eli Cohen;
net...@vger.kernel.org; linux-r...@vger.kernel.org
Subject: Re: linux-next: Tree for Jul 11 (mellanox/mlx5)
On 07/10/13 21:17, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20130710:
>
on i386:
ERROR: "__udivdi3" [drivers/net/
; linux-kernel@vger.kernel.org; Eli Cohen;
net...@vger.kernel.org; linux-r...@vger.kernel.org
Subject: Re: linux-next: Tree for Jul 11 (mellanox/mlx5)
On 07/10/13 21:17, Stephen Rothwell wrote:
Hi all,
Changes since 20130710:
on i386:
ERROR: __udivdi3 [drivers/net/ethernet/mellanox/mlx5/core
On Fri, Jul 12, 2013 at 2:47 AM, Randy Dunlap rdun...@infradead.org wrote:
On 07/10/13 21:17, Stephen Rothwell wrote:
Hi all,
Changes since 20130710:
on x86_64:
# CONFIG_USB_GADGET is not set
ERROR: usb_gadget_map_request [drivers/usb/chipidea/ci_hdrc.ko] undefined!
ERROR:
Hi all,
Changes since 20130710:
The slab tree lost its build failure.
The akpm tree lost a patch that turned up elsewhere.
I have created today's linux-next tree at
Hi all,
Changes since 20130710:
The slab tree lost its build failure.
The akpm tree lost a patch that turned up elsewhere.
I have created today's linux-next tree at
21 matches
Mail list logo
