On Thu, 7 May 2020, Randy Dunlap wrote:
> > Changes since 20200505:
> >
>
>
> on i386 or x86_64:
>
> ERROR: modpost: "usb_hid_driver" [drivers/hid/hid-asus.ko] undefined!
> or
> (when builtin:)
> ld: drivers/hid/hid-asus.o: in function `asus_probe':
> hid-asus.c:(.text+0x60f): undefined refere
On 5/7/20 1:15 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20200505:
>
on i386 or x86_64:
ERROR: modpost: "usb_hid_driver" [drivers/hid/hid-asus.ko] undefined!
or
(when builtin:)
ld: drivers/hid/hid-asus.o: in function `asus_probe':
hid-asus.c:(.text+0x60f): undefined reference to
Hi all,
Changes since 20200505:
My fixes tree contains:
bbefc924d0ff ("ubsan: disable UBSAN_ALIGNMENT under COMPILE_TEST")
7cb1d38f52b1 ("drm/msm: Fix undefined "rd_full" link error")
41ef83a65305 ("device_cgroup: Fix RCU list debugging warning")
d58ae1991898 ("ipmr: Add lockdep expressi
Hi all,
Changes since 20190506:
The kbuild tree lost its build failures.
The vfs tree gained a conflict against the fuse tree.
Non-merge commits (relative to Linus' tree): 11387
10878 files changed, 492059 insertions(+), 314852 deletions(-)
On 05/06/2018 10:31 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20180504:
>
on i386:
net/xdp/xdp_umem.o: In function `xdp_umem_reg':
xdp_umem.c:(.text+0x47e): undefined reference to `__udivdi3'
--
~Randy
Hi Geert,
On Mon, 7 May 2018 14:13:27 +0200 Geert Uytterhoeven
wrote:
>
> On Mon, May 7, 2018 at 7:31 AM, Stephen Rothwell
> wrote:
> > Status of my local build tests will be at
> > http://kisskb.ellerman.id.au/linux-next .
>
> Oops, Service Unavailable
I restarted docker and it seems to h
Hi Stephen,
On Mon, May 7, 2018 at 7:31 AM, Stephen Rothwell wrote:
> Status of my local build tests will be at
> http://kisskb.ellerman.id.au/linux-next .
Oops, Service Unavailable
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 --
Hi all,
Changes since 20180504:
The net-next tree gained a conflict against the net tree.
The tip tree gained conflicts against the bpf-next tree.
Non-merge commits (relative to Linus' tree): 4139
3963 files changed, 164135 insertions(+), 75455 deletions(-)
---
On Fri, May 8, 2015 at 3:54 AM, Guenter Roeck wrote:
> On Thu, May 07, 2015 at 04:47:15PM +1000, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20150506:
>>
>> The ext4 tree gained a build failure so I used the version from
>> next-20150506.
>>
>> The vfs tree gained a conflict against the
On Thu, May 07, 2015 at 04:47:15PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20150506:
>
> The ext4 tree gained a build failure so I used the version from
> next-20150506.
>
> The vfs tree gained a conflict against the f2fs tree.
>
> The rcu tree gained conflicts against the ti
On Thu, May 07, 2015 at 04:47:15PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20150506:
>
> The ext4 tree gained a build failure so I used the version from
> next-20150506.
>
> The vfs tree gained a conflict against the f2fs tree.
>
> The rcu tree gained conflicts against the ti
Hi all,
Changes since 20150506:
The ext4 tree gained a build failure so I used the version from
next-20150506.
The vfs tree gained a conflict against the f2fs tree.
The rcu tree gained conflicts against the tip tree.
Non-merge commits (relative to Linus' tree): 2460
2454 files changed, 114321
On 05/07/2014 02:56 PM, Stephen Rothwell wrote:
> Hi Randy,
>
> On Wed, 07 May 2014 13:52:02 -0700 Randy Dunlap wrote:
>>
>> I was away for one week. Did I miss some new instructions about
>> building linux-next?
>
> Nothing that I know of.
>
>>
>> I get a thousands of messages like these:
>
Hi Randy,
On Wed, 07 May 2014 13:52:02 -0700 Randy Dunlap wrote:
>
> I was away for one week. Did I miss some new instructions about
> building linux-next?
Nothing that I know of.
>
> I get a thousands of messages like these:
What config? What arch? Did you just do "make oldconfig"?
> WAR
On 05/07/2014 12:33 AM, Stephen Rothwell wrote:
> Hi all,
>
> This tree still fails (more than usual) the powerpc allyesconfig build
> and also the celleb_defconfig.
>
> Changes since 20140506:
>
I was away for one week. Did I miss some new instructions about
building linux-next?
I get a thou
Hi all,
This tree still fails (more than usual) the powerpc allyesconfig build
and also the celleb_defconfig.
Changes since 20140506:
The powerpc tree still had its build failure.
The drm tree gained a conflict against the drm-intel-fixes tree.
Non-merge commits (relative to Linus' tree): 4132
On Tue, May 07, 2013 at 10:21:21AM -0700, Randy Dunlap wrote:
> On 05/06/13 20:49, Stephen Rothwell wrote:
> > Hi all,
> >
> > Please do not add any v3.11 destined work to your linux-next included
> > branches until after v3.10-rc1 is released.
> >
> > I am receiving a (un)reasonable number of co
On 05/07/2013 07:08 PM, Randy Dunlap wrote:
> On 05/06/13 20:49, Stephen Rothwell wrote:
>> Hi all,
>>
>> Please do not add any v3.11 destined work to your linux-next included
>> branches until after v3.10-rc1 is released.
>>
>> I am receiving a (un)reasonable number of conflicts from there being
>
On 05/06/13 20:49, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any v3.11 destined work to your linux-next included
> branches until after v3.10-rc1 is released.
>
> I am receiving a (un)reasonable number of conflicts from there being
> multiple copies of some commits in various trees.
On 05/06/13 20:49, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any v3.11 destined work to your linux-next included
> branches until after v3.10-rc1 is released.
>
> I am receiving a (un)reasonable number of conflicts from there being
> multiple copies of some commits in various trees.
On 05/06/13 20:49, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any v3.11 destined work to your linux-next included
> branches until after v3.10-rc1 is released.
>
> I am receiving a (un)reasonable number of conflicts from there being
> multiple copies of some commits in various trees.
Hi all,
Please do not add any v3.11 destined work to your linux-next included
branches until after v3.10-rc1 is released.
I am receiving a (un)reasonable number of conflicts from there being
multiple copies of some commits in various trees. Please clean this up
and resist the temptataion to reb
22 matches
Mail list logo
