Hi all,
Changes since 20200715:
My fixes tree contains:
dbf24e30ce2e ("device_cgroup: Fix RCU list debugging warning")
The net-next tree gained a conflict against the bpf tree.
The block tree gained lost its build failure and runtime problem.
The security tree still had its build failure fo
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 20190715:
The kbuild tree gained a build failure for which I reverted 4 commits.
The pm tree lost its build failure.
The rdma tree gained a conflict against the v4
Hi all,
Changes since 20180713:
The arm-soc tree gained a build failure so I used the version from
next-20180713.
Non-merge commits (relative to Linus' tree): 6029
5901 files changed, 216652 insertions(+), 121372 deletions(-)
Hi all,
For those that care: I have stopped signing these messages because
vger's mailing list software destroys the signatures and then Google
(at least) assumes that they are spam. I could clear sign them instead
(if anyone thinks that is worth while).
Changes since 20150715:
Removed tree: i
On Wed, Jul 16, 2014 at 11:14 PM, Stephen Rothwell
wrote:
> Hi Nick,
>
> On Wed, 16 Jul 2014 22:01:35 -0400 Nick Krause wrote:
>>
>> Absolutely , I am using the latest kernel rc from git. I am using gcc
>> 4.8.3 and binutils 2.83.91.
>
> Then that has nothing to do with me ... I am the linux-nex
Hi Nick,
On Wed, 16 Jul 2014 22:01:35 -0400 Nick Krause wrote:
>
> Absolutely , I am using the latest kernel rc from git. I am using gcc
> 4.8.3 and binutils 2.83.91.
Then that has nothing to do with me ... I am the linux-next
maintainer. I just happen to use the same build test system as is al
On Wed, Jul 16, 2014 at 9:47 PM, Stephen Rothwell wrote:
> Hi Nick,
>
> On Wed, 16 Jul 2014 21:16:16 -0400 Nick Krause wrote:
>>
>> > On Wed, 16 Jul 2014 20:45:25 -0400 Nick Krause wrote:
>> >>
>> >> On Wed, Jul 16, 2014 at 4:45 AM, Stephen Rothwell
>> >> wrote:
>> >> >
>> >> > Status of my lo
Hi Nick,
On Wed, 16 Jul 2014 21:16:16 -0400 Nick Krause wrote:
>
> > On Wed, 16 Jul 2014 20:45:25 -0400 Nick Krause wrote:
> >>
> >> On Wed, Jul 16, 2014 at 4:45 AM, Stephen Rothwell
> >> wrote:
> >> >
> >> > Status of my local build tests will be at
> >> > http://kisskb.ellerman.id.au/linux-n
>
> On Wed, 16 Jul 2014 20:45:25 -0400 Nick Krause wrote:
>>
>> On Wed, Jul 16, 2014 at 4:45 AM, Stephen Rothwell
>> wrote:
>> >
>> > Status of my local build tests will be at
>> > http://kisskb.ellerman.id.au/linux-next .
>
>> I am trying to get the maintainers to clean up still failing builds.
Hi Nick,
[Please trim your replies to just the bit (if any) that you are
referring to]
On Wed, 16 Jul 2014 20:45:25 -0400 Nick Krause wrote:
>
> On Wed, Jul 16, 2014 at 4:45 AM, Stephen Rothwell
> wrote:
> >
> > Status of my local build tests will be at
> > http://kisskb.ellerman.id.au/linux-n
On Wed, Jul 16, 2014 at 4:45 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20140715:
>
> The v4l-dvb tree lost its build failure.
>
> The wireless-next tree gained a build failure so I used the version
> from next-20140715.
>
> The infiniband tree gained a conflict against the net-next t
Hi all,
Changes since 20140715:
The v4l-dvb tree lost its build failure.
The wireless-next tree gained a build failure so I used the version
from next-20140715.
The infiniband tree gained a conflict against the net-next tree.
The staging tree gained conflict against the net-next and v4l-dvb tr
Hi all,
Changes since 20130712:
New tree: ptr-ret
Removed tree: cpuidle (at maintainers request)
The drm-intel tree gained a conflict against the drm-intel-fixes tree.
The sound-asoc tree gained a build failure so I used the version from
next-20130715.
The akpm tree gained conflicts against t
13 matches
Mail list logo
