Hi all,
Changes since 20200701:
New tree: memblock
My fixes tree contains:
dbf24e30ce2e ("device_cgroup: Fix RCU list debugging warning")
b236d81d9e4f ("powerpc/boot/dts: Fix dtc "pciex" warnings")
The tip tree still had one build failure for which I reverted a commit.
Non-merge commits
On Wed, Jul 03, 2019 at 02:46:14PM -0500, Josh Poimboeuf wrote:
> On Wed, Jul 03, 2019 at 02:45:28PM -0500, Josh Poimboeuf wrote:
> > On Wed, Jul 03, 2019 at 10:23:21AM -0700, Randy Dunlap wrote:
> > > On 7/3/19 9:44 AM, Josh Poimboeuf wrote:
> > > > On Tue, Jul 02, 2019 at 11:47:02AM -0700, Randy
On Wed, Jul 03, 2019 at 02:45:28PM -0500, Josh Poimboeuf wrote:
> On Wed, Jul 03, 2019 at 10:23:21AM -0700, Randy Dunlap wrote:
> > On 7/3/19 9:44 AM, Josh Poimboeuf wrote:
> > > On Tue, Jul 02, 2019 at 11:47:02AM -0700, Randy Dunlap wrote:
> > >> On 7/2/19 2:51 AM, Stephen Rothwell wrote:
> > >>>
On Wed, Jul 03, 2019 at 10:23:21AM -0700, Randy Dunlap wrote:
> On 7/3/19 9:44 AM, Josh Poimboeuf wrote:
> > On Tue, Jul 02, 2019 at 11:47:02AM -0700, Randy Dunlap wrote:
> >> On 7/2/19 2:51 AM, Stephen Rothwell wrote:
> >>> Hi all,
> >>>
> >>> Changes since 20190701:
> >>>
> >>
> >> on x86_64:
>
On Tue, Jul 02, 2019 at 11:47:02AM -0700, Randy Dunlap wrote:
> On 7/2/19 2:51 AM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20190701:
> >
>
> on x86_64:
>
> kernel/bpf/core.o: warning: objtool: ___bpf_prog_run()+0x22: can't find
> switch jump table
I don't see it on current
On 7/2/19 2:51 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20190701:
>
on x86_64:
kernel/bpf/core.o: warning: objtool: ___bpf_prog_run()+0x22: can't find switch
jump table
--
~Randy
On Tue, Jul 02, 2019 at 01:03:22PM +0100, Will Deacon wrote:
> Joerg -- please can you take this on top of the SMMUv3 patches queued
> for 5.3?
Applied, thanks.
Hi Will,
On 2019/7/2 20:03, Will Deacon wrote:
> [+Joerg]
>
> On Tue, Jul 02, 2019 at 06:40:45PM +0800, Zhangshaokun wrote:
>> +Cc: Will Deacon
>>
>> There is a compiler failure on arm64 platform, as follow:
>> In file included from ./include/linux/list.h:9:0,
>> from
[+Joerg]
On Tue, Jul 02, 2019 at 06:40:45PM +0800, Zhangshaokun wrote:
> +Cc: Will Deacon
>
> There is a compiler failure on arm64 platform, as follow:
> In file included from ./include/linux/list.h:9:0,
> from ./include/linux/kobject.h:19,
> from
+Cc: Will Deacon
There is a compiler failure on arm64 platform, as follow:
In file included from ./include/linux/list.h:9:0,
from ./include/linux/kobject.h:19,
from ./include/linux/of.h:17,
from ./include/linux/irqdomain.h:35,
Hi all,
Changes since 20190701:
New trees: iomap, djw-vfs
The m68knommu tree gained conflicts against the m68k tree.
The xfs tree lost its build failure.
The pm tree lost its build failure.
The rdma tree still had its build failures so I used the version from
next-20190628.
The net-next
Randy Dunlap writes:
> [add other maintainers]
> on i386 or x86_64:
>
> builtin:
> sound/soc/pxa/pxa-ssp.o:(.rodata+0x228): undefined reference to
> `pxa2xx_soc_pcm_new'
> sound/soc/pxa/pxa-ssp.o:(.rodata+0x22c): undefined reference to
> `pxa2xx_pcm_free_dma_buffers'
>
Randy Dunlap writes:
> [add other maintainers]
> on i386 or x86_64:
>
> builtin:
> sound/soc/pxa/pxa-ssp.o:(.rodata+0x228): undefined reference to
> `pxa2xx_soc_pcm_new'
> sound/soc/pxa/pxa-ssp.o:(.rodata+0x22c): undefined reference to
> `pxa2xx_pcm_free_dma_buffers'
>
[add other maintainers]
On 07/02/18 09:09, Randy Dunlap wrote:
> On 07/01/18 21:51, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20180629:
>>
>
> on i386 or x86_64:
>
> builtin:
> sound/soc/pxa/pxa-ssp.o:(.rodata+0x228): undefined reference to
> `pxa2xx_soc_pcm_new'
>
[add other maintainers]
On 07/02/18 09:09, Randy Dunlap wrote:
> On 07/01/18 21:51, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20180629:
>>
>
> on i386 or x86_64:
>
> builtin:
> sound/soc/pxa/pxa-ssp.o:(.rodata+0x228): undefined reference to
> `pxa2xx_soc_pcm_new'
>
On 07/01/18 21:51, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20180629:
>
on i386 or x86_64:
builtin:
sound/soc/pxa/pxa-ssp.o:(.rodata+0x228): undefined reference to
`pxa2xx_soc_pcm_new'
sound/soc/pxa/pxa-ssp.o:(.rodata+0x22c): undefined reference to
`pxa2xx_pcm_free_dma_buffers'
On 07/01/18 21:51, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20180629:
>
on i386 or x86_64:
builtin:
sound/soc/pxa/pxa-ssp.o:(.rodata+0x228): undefined reference to
`pxa2xx_soc_pcm_new'
sound/soc/pxa/pxa-ssp.o:(.rodata+0x22c): undefined reference to
`pxa2xx_pcm_free_dma_buffers'
Hi all,
Changes since 20180629:
New tree: siox
The btrfs-kdave tree lost its build failure.
The fbdev tree lost its build failure.
The net-next tree gained conflicts against the net and rdma trees.
The akpm-current tree still had its build failure for which I reverted
a commit.
Non-merge
Hi all,
Changes since 20180629:
New tree: siox
The btrfs-kdave tree lost its build failure.
The fbdev tree lost its build failure.
The net-next tree gained conflicts against the net and rdma trees.
The akpm-current tree still had its build failure for which I reverted
a commit.
Non-merge
Hi all,
Please do not add any v4.3 related material to your linux-next included
branches until after v4.2-rc1 is released.
Changes since 20150701:
The kbuild tree gained a conflict against Linus' tree.
I dropped a patch from the akpm tree since the commit it was fixing has
been removed.
Hi all,
Please do not add any v4.3 related material to your linux-next included
branches until after v4.2-rc1 is released.
Changes since 20150701:
The kbuild tree gained a conflict against Linus' tree.
I dropped a patch from the akpm tree since the commit it was fixing has
been removed.
Hi all,
Changes since 20140701:
My fixes tree contains:
powerpc: Disable RELOCATABLE for COMPILE_TEST with PPC64
The arm-perf tree gained a conflict against to arm tree.
The net-next tree lost its build failure.
The staging tree still had its build failure for which I disabled a
Hi all,
Changes since 20140701:
My fixes tree contains:
powerpc: Disable RELOCATABLE for COMPILE_TEST with PPC64
The arm-perf tree gained a conflict against to arm tree.
The net-next tree lost its build failure.
The staging tree still had its build failure for which I disabled a
On Tue, Jul 2, 2013 at 9:07 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20130701:
>
> The powerpc tree gained a build failure so I used the version from
> next-20130701.
>
> The regulator tree lost its build failure.
>
> The arm-soc tree gained conflicts against the l2-mtd tree.
>
>
On Tue, Jul 2, 2013 at 9:07 AM, Stephen Rothwell s...@canb.auug.org.au wrote:
Hi all,
Changes since 20130701:
The powerpc tree gained a build failure so I used the version from
next-20130701.
The regulator tree lost its build failure.
The arm-soc tree gained conflicts against the l2-mtd
25 matches
Mail list logo
