Hi all,
Please do not add any code destined for v5.2 to your linux-next included
branches until after v5.1-rc1 has been released.
News: I will not be doing linux-next releases from next Thursday (Mar
7) to the following Friday (Mar 15). Sorry this happened to fall
across most of the merge window
Hi all,
Changes since 20180305:
The mali-dp tree gained a conflict against the drm-misc tree.
Non-merge commits (relative to Linus' tree): 4880
5418 files changed, 202951 insertions(+), 143721 deletions(-)
I have cre
Hi all,
Changes since 20170303:
Removed tree: blackfin (will be replaced)
The vfs tree lost its build failure.
Non-merge commits (relative to Linus' tree): 361
499 files changed, 13261 insertions(+), 3007 deletions(-)
---
Hi all,
Changes since 20150305:
The net-next tree lost its build failure.
The vhost tree gained a conflict against the virtio tree.
Non-merge commits (relative to Linus' tree): 2757
2807 files changed, 87638 insertions(+), 60274 deletions(-)
---
> > Hi all,
> >
> > There may be build failures in this tree due to the percpu changes in the
> > akpm tree.
> >
> > This tree fails (more than usual) the powerpc allyesconfig build.
> >
> > Changes since 20140305:
> >
>
> In linux-next-20140305 and -20140306:
>
> ERROR: "regmap_del_irq_chip"
On 03/06/2014 12:48 AM, Stephen Rothwell wrote:
> Hi all,
>
> There may be build failures in this tree due to the percpu changes in the
> akpm tree.
>
> This tree fails (more than usual) the powerpc allyesconfig build.
>
> Changes since 20140305:
>
In linux-next-20140305 and -20140306:
ERROR:
Hi all,
There may be build failures in this tree due to the percpu changes in the
akpm tree.
This tree fails (more than usual) the powerpc allyesconfig build.
Changes since 20140305:
The powerpc tree still had its build failure.
The wireless-next tree still had its build failure so I reverted
On Thu, Mar 7, 2013 at 11:33 AM, Jiri Kosina wrote:
> On Thu, 7 Mar 2013, Benjamin Tissoires wrote:
>
>> You should have at least one other patch for hid-mt:
>> https://patchwork.kernel.org/patch/2193641/
>
> Ah, right, that one is in my queue as well, sorry for not mentioning it in
> my previous
On Thu, 7 Mar 2013, Benjamin Tissoires wrote:
> You should have at least one other patch for hid-mt:
> https://patchwork.kernel.org/patch/2193641/
Ah, right, that one is in my queue as well, sorry for not mentioning it in
my previous post.
That doesn't remove the direct call either though.
> A
On Thu, Mar 7, 2013 at 11:09 AM, Jiri Kosina wrote:
> On Thu, 7 Mar 2013, Benjamin Tissoires wrote:
>
>> > on i386 and x86_64:
>> >
>>
>> Sorry, it looks like my patches went not very smoothly.
>>
>> > ERROR: "usb_control_msg" [drivers/hid/hid-multitouch.ko] undefined!
>>
>> I've submitted a new p
On Thu, 7 Mar 2013, Benjamin Tissoires wrote:
> > on i386 and x86_64:
> >
>
> Sorry, it looks like my patches went not very smoothly.
>
> > ERROR: "usb_control_msg" [drivers/hid/hid-multitouch.ko] undefined!
>
> I've submitted a new patch removing this direct call. Maybe we should
> change the
Hi Randy,
On Wed, Mar 6, 2013 at 8:26 PM, Randy Dunlap wrote:
> On 03/05/13 16:50, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20130305:
>>
>
> on i386 and x86_64:
>
Sorry, it looks like my patches went not very smoothly.
> ERROR: "usb_control_msg" [drivers/hid/hid-multitouch.ko] und
On 03/05/13 16:50, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20130305:
>
on i386 and x86_64:
ERROR: "usb_control_msg" [drivers/hid/hid-multitouch.ko] undefined!
ERROR: "usb_ifnum_to_if" [drivers/hid/hid-holtek-kbd.ko] undefined!
when CONFIG_USB_SUPPORT is not enabled.
Should these d
Hi all,
Changes since 20130305:
The staging tree gained a build failure for which I applied a patch.
The gpio tree gained a build failure for which I reverted a commit.
The akpm tree still had its 2 build failures for which I reverted 2
commits.
14 matches
Mail list logo
