On Tue, 10 Nov 2020 at 14:54, Marco Elver wrote:
>
> On Tue, 10 Nov 2020 at 10:36, Dmitry Vyukov wrote:
> [...]
> > > > On Tue, Nov 10, 2020 at 8:50 AM Anders Roxell
> > > > wrote:
> [...]
> > > > > When building an arm64 allmodconfig and booting up that in qemu I see
> > > > >
> > > > >
On Tue, 10 Nov 2020 at 10:36, Dmitry Vyukov wrote:
[...]
> > > On Tue, Nov 10, 2020 at 8:50 AM Anders Roxell
> > > wrote:
[...]
> > > > When building an arm64 allmodconfig and booting up that in qemu I see
> > > >
> > > > [10011.092394][ T28] task:kworker/0:2 state:D stack:26896 pid:
> >
On Tue, Nov 10, 2020 at 10:25 AM Anders Roxell wrote:
>
> On Tue, 10 Nov 2020 at 10:17, Dmitry Vyukov wrote:
> >
> > On Tue, Nov 10, 2020 at 8:50 AM Anders Roxell
> > wrote:
> > >
> > > On Thu, 5 Nov 2020 at 07:06, Stephen Rothwell
> > > wrote:
> > > >
> > > > Hi all,
> > > >
> > > > Changes
On Tue, 10 Nov 2020 at 10:17, Dmitry Vyukov wrote:
>
> On Tue, Nov 10, 2020 at 8:50 AM Anders Roxell
> wrote:
> >
> > On Thu, 5 Nov 2020 at 07:06, Stephen Rothwell wrote:
> > >
> > > Hi all,
> > >
> > > Changes since 20201104:
> >
> > When building an arm64 allmodconfig and booting up that in
On Tue, Nov 10, 2020 at 8:50 AM Anders Roxell wrote:
>
> On Thu, 5 Nov 2020 at 07:06, Stephen Rothwell wrote:
> >
> > Hi all,
> >
> > Changes since 20201104:
>
> When building an arm64 allmodconfig and booting up that in qemu I see
>
> [10011.092394][ T28] task:kworker/0:2 state:D
On Thu, 5 Nov 2020 at 07:06, Stephen Rothwell wrote:
>
> Hi all,
>
> Changes since 20201104:
When building an arm64 allmodconfig and booting up that in qemu I see
[10011.092394][ T28] task:kworker/0:2 state:D stack:26896 pid:
1840 ppid: 2 flags:0x0428
[10022.368093][ T28]
On 11/4/20 10:06 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20201104:
>
> The drm-intel-fixes tree lost its build failure.
>
> The drm-msm tree gained conflicts against the drm and drm-misc trees.
>
> The mfd tree gained a build failure so I used the version from
> next-20201104.
On 11/4/20 10:06 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20201104:
>
on i386:
ERROR: modpost: "charlcd_backlight" [drivers/auxdisplay/hd44780_common.ko]
undefined!
Full randconfig file is attached.
--
~Randy
Reported-by: Randy Dunlap
#
# Automatically generated file; DO
Hi all,
Changes since 20201104:
The drm-intel-fixes tree lost its build failure.
The drm-msm tree gained conflicts against the drm and drm-misc trees.
The mfd tree gained a build failure so I used the version from
next-20201104.
The pinctrl tree lost its build failure.
The akpm-current tree
On 11/4/18 9:51 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20181102:
>
> Non-merge commits (relative to Linus' tree): 418
on i386 or x86_64:
ld: net/ipv6/af_inet6.o: in function `inet6_init':
af_inet6.c:(.init.text+0x285): undefined reference to `ipv6_anycast_init'
ld:
On 11/4/18 9:51 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20181102:
>
> Non-merge commits (relative to Linus' tree): 418
on i386 or x86_64:
ld: net/ipv6/af_inet6.o: in function `inet6_init':
af_inet6.c:(.init.text+0x285): undefined reference to `ipv6_anycast_init'
ld:
Hi all,
Changes since 20181102:
Non-merge commits (relative to Linus' tree): 418
585 files changed, 22874 insertions(+), 5819 deletions(-)
I have created today's linux-next tree at
Hi all,
Changes since 20181102:
Non-merge commits (relative to Linus' tree): 418
585 files changed, 22874 insertions(+), 5819 deletions(-)
I have created today's linux-next tree at
Hi all,
Please do *not* add any material intended for v4.5 to your linux-next
included branches until after v4.4-rc1 has been released.
Changes since 20151104:
The battery tree still had its build failure so I used the version from
next-20150925.
The mailbox tree lost its build failure.
The
Hi all,
Please do *not* add any material intended for v4.5 to your linux-next
included branches until after v4.4-rc1 has been released.
Changes since 20151104:
The battery tree still had its build failure so I used the version from
next-20150925.
The mailbox tree lost its build failure.
The
On Wed, Nov 05, 2014 at 05:53:30PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Due to a move of office, there will not be a linux-next release on
> Friday (and maybe Monday).
>
> Changes since 20141104:
>
> The f2fs tree gained a build failure so I used the version from
> next-20141104.
>
>
On Wed, Nov 05, 2014 at 05:53:30PM +1100, Stephen Rothwell wrote:
Hi all,
Due to a move of office, there will not be a linux-next release on
Friday (and maybe Monday).
Changes since 20141104:
The f2fs tree gained a build failure so I used the version from
next-20141104.
The mfd tree
Hi all,
Due to a move of office, there will not be a linux-next release on
Friday (and maybe Monday).
Changes since 20141104:
The f2fs tree gained a build failure so I used the version from
next-20141104.
The mfd tree lost its build failure.
The iommu tree gained a build failure so I used the
Hi all,
Due to a move of office, there will not be a linux-next release on
Friday (and maybe Monday).
Changes since 20141104:
The f2fs tree gained a build failure so I used the version from
next-20141104.
The mfd tree lost its build failure.
The iommu tree gained a build failure so I used the
On 11/04/13 23:16, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20131104:
on i386:
drivers/tty/serial/xilinx_uartps.c: In function 'xuartps_isr':
drivers/tty/serial/xilinx_uartps.c:247:13: error: 'struct uart_port' has no
member named 'sysrq'
--
~Randy
--
To unsubscribe from this
On 11/04/13 23:16, Stephen Rothwell wrote:
Hi all,
Changes since 20131104:
on i386:
drivers/tty/serial/xilinx_uartps.c: In function 'xuartps_isr':
drivers/tty/serial/xilinx_uartps.c:247:13: error: 'struct uart_port' has no
member named 'sysrq'
--
~Randy
--
To unsubscribe from this list:
Hi all,
Changes since 20131104:
Removed tree: bcon
The sound-asoc tree lost its build failure.
The device-mapper tree gained a build failure for which I applied a merge
fix patch.
The modules tree still produced a very large number of warnings so I used
the version from next-20131101.
The
Hi all,
Changes since 20131104:
Removed tree: bcon
The sound-asoc tree lost its build failure.
The device-mapper tree gained a build failure for which I applied a merge
fix patch.
The modules tree still produced a very large number of warnings so I used
the version from next-20131101.
The
Hi all,
Changes since 20121102:
The v4l-dvb tree still had its build failure so I used the version from
next-20121026.
The thermal tree gained a conflict against Linus' tree.
The modules tree lost its build failure.
The usb tree lost its build failures.
The signal tree gained a conflict
Hi all,
Changes since 20121102:
The v4l-dvb tree still had its build failure so I used the version from
next-20121026.
The thermal tree gained a conflict against Linus' tree.
The modules tree lost its build failure.
The usb tree lost its build failures.
The signal tree gained a conflict
25 matches
Mail list logo
