Hi all,
Since the merge window is open, please do not add any v5.11 material to
your linux-next included branches until after v5.10-rc1 has been released.
News: there will be no linux-next releases next Monday or Tuesday.
Changes since 20201015:
Undropped tree: btrfs
The wireless-drivers tree
Hi all,
Changes since 20191015:
New tree: cel
The pm tree lost its build failure.
The drm-misc tree gained a semantic conflict against the amdgpu tree.
The sound-asoc tree gained a conflict against the sound tree.
The devicetree tree gained a conflict against Linus' tree.
The drivers-x86
Hi all,
Changes since 20181015:
The jc_docs tree gained a conflict against the pci tree
The netfilter-next tree gained a build failure so I used the version
from next-20181015.
The block tree gained a conflict against the pci tree.
I added a patch to the akpm tree to fix my qemu PowerPC boot
Hi all,
Changes since 20181015:
The jc_docs tree gained a conflict against the pci tree
The netfilter-next tree gained a build failure so I used the version
from next-20181015.
The block tree gained a conflict against the pci tree.
I added a patch to the akpm tree to fix my qemu PowerPC boot
Hi all,
Changes since 20161014:
The net tree gained a conflict against Linus' tree.
The akpm-current tree still had its build failures for which I applied
2 patches.
Non-merge commits (relative to Linus' tree): 389
614 files changed, 17748 insertions(+), 3167 deletions(-)
Hi all,
Changes since 20161014:
The net tree gained a conflict against Linus' tree.
The akpm-current tree still had its build failures for which I applied
2 patches.
Non-merge commits (relative to Linus' tree): 389
614 files changed, 17748 insertions(+), 3167 deletions(-)
Hi all,
Changes since 20151015:
The asm-generic tree lost its build failure.
The arm-soc tree lost its build failure.
I used the h8300 tree from next-20150828 since the current tree no
contains a rebased part of Linus' tree.
The slave-dma tree still had its build failure for which I applied a
Hi all,
Changes since 20151015:
The asm-generic tree lost its build failure.
The arm-soc tree lost its build failure.
I used the h8300 tree from next-20150828 since the current tree no
contains a rebased part of Linus' tree.
The slave-dma tree still had its build failure for which I applied a
On Thu, Oct 16, 2014 at 04:11:28PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any material intended for v3.19 to your linux-next
> included trees until after v3.18-rc1 has been released.
>
> Changes since 20141015:
>
> The net tree lost its build failure.
>
> The thermal
On Thu, Oct 16, 2014 at 04:11:28PM +1100, Stephen Rothwell wrote:
Hi all,
Please do not add any material intended for v3.19 to your linux-next
included trees until after v3.18-rc1 has been released.
Changes since 20141015:
The net tree lost its build failure.
The thermal tree gained
Hi all,
Please do not add any material intended for v3.19 to your linux-next
included trees until after v3.18-rc1 has been released.
Changes since 20141015:
The net tree lost its build failure.
The thermal tree gained a build failure for which I reverted a commit.
The akpm-current tree gained
Hi all,
Please do not add any material intended for v3.19 to your linux-next
included trees until after v3.18-rc1 has been released.
Changes since 20141015:
The net tree lost its build failure.
The thermal tree gained a build failure for which I reverted a commit.
The akpm-current tree gained
On 10/16/2013 11:51 AM, Thierry Reding wrote:
Hi all,
I've uploaded today's linux-next tree to the master branch of the
repository below:
git://gitorious.org/thierryreding/linux-next.git
A next-20131016 tag is also provided for convenience.
Gained two new conflicts, but nothing too
On 10/16/13 15:39, Stephen Hemminger wrote:
> On Wed, 16 Oct 2013 14:48:32 -0700
> Randy Dunlap wrote:
>
>> On 10/16/13 11:51, Thierry Reding wrote:
>>> Hi all,
>>>
>>> I've uploaded today's linux-next tree to the master branch of the
>>> repository below:
>>>
>>>
On Wed, 16 Oct 2013 14:48:32 -0700
Randy Dunlap wrote:
> On 10/16/13 11:51, Thierry Reding wrote:
> > Hi all,
> >
> > I've uploaded today's linux-next tree to the master branch of the
> > repository below:
> >
> > git://gitorious.org/thierryreding/linux-next.git
> >
> > A
On 10/16/13 11:51, Thierry Reding wrote:
> Hi all,
>
> I've uploaded today's linux-next tree to the master branch of the
> repository below:
>
> git://gitorious.org/thierryreding/linux-next.git
>
> A next-20131016 tag is also provided for convenience.
>
> Gained two new conflicts, but
Hi all,
I've uploaded today's linux-next tree to the master branch of the
repository below:
git://gitorious.org/thierryreding/linux-next.git
A next-20131016 tag is also provided for convenience.
Gained two new conflicts, but nothing too exciting. x86 and ARM default
configurations as
Hi all,
I've uploaded today's linux-next tree to the master branch of the
repository below:
git://gitorious.org/thierryreding/linux-next.git
A next-20131016 tag is also provided for convenience.
Gained two new conflicts, but nothing too exciting. x86 and ARM default
configurations as
On 10/16/13 11:51, Thierry Reding wrote:
Hi all,
I've uploaded today's linux-next tree to the master branch of the
repository below:
git://gitorious.org/thierryreding/linux-next.git
A next-20131016 tag is also provided for convenience.
Gained two new conflicts, but nothing
On Wed, 16 Oct 2013 14:48:32 -0700
Randy Dunlap rdun...@infradead.org wrote:
On 10/16/13 11:51, Thierry Reding wrote:
Hi all,
I've uploaded today's linux-next tree to the master branch of the
repository below:
git://gitorious.org/thierryreding/linux-next.git
A
On 10/16/13 15:39, Stephen Hemminger wrote:
On Wed, 16 Oct 2013 14:48:32 -0700
Randy Dunlap rdun...@infradead.org wrote:
On 10/16/13 11:51, Thierry Reding wrote:
Hi all,
I've uploaded today's linux-next tree to the master branch of the
repository below:
On 10/16/2013 11:51 AM, Thierry Reding wrote:
Hi all,
I've uploaded today's linux-next tree to the master branch of the
repository below:
git://gitorious.org/thierryreding/linux-next.git
A next-20131016 tag is also provided for convenience.
Gained two new conflicts, but nothing too
On Tue, Oct 16, 2012 at 4:05 PM, Randy Dunlap wrote:
> On 10/15/2012 08:58 PM, Stephen Rothwell wrote:
>
>> Hi all,
>>
>> The merge window has closed, feel free to add new stuff again.
>>
>> Changes since 201201015:
>>
patch already sent to Dave:
On Tue, Oct 16, 2012 at 4:05 PM, Randy Dunlap rdun...@xenotime.net wrote:
On 10/15/2012 08:58 PM, Stephen Rothwell wrote:
Hi all,
The merge window has closed, feel free to add new stuff again.
Changes since 201201015:
patch already sent to Dave:
Hi all,
The merge window has closed, feel free to add new stuff again.
Changes since 201201015:
New tree: cortex
Dropped Tree: cortex (complex merge conflict)
Removed tree: kmemleak (maintainer suggested)
The l2-mtd tree still had its build failure so I used the version from
next-20121011.
Hi all,
The merge window has closed, feel free to add new stuff again.
Changes since 201201015:
New tree: cortex
Dropped Tree: cortex (complex merge conflict)
Removed tree: kmemleak (maintainer suggested)
The l2-mtd tree still had its build failure so I used the version from
next-20121011.
26 matches
Mail list logo
