On Tue, Mar 16, 2021 at 12:05 AM Randy Dunlap wrote:
>
> On 3/14/21 10:24 PM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Warning: Some of the branches in linux-next are still based on v5.12-rc1,
> > so please be careful if you are trying to bisect a bug.
> >
> > News: if your -next included tree
On 3/14/21 10:24 PM, Stephen Rothwell wrote:
> Hi all,
>
> Warning: Some of the branches in linux-next are still based on v5.12-rc1,
> so please be careful if you are trying to bisect a bug.
>
> News: if your -next included tree is based on Linus' tree tag
> v5.12-rc1{,-dontuse} (or somewhere bet
Hi all,
Warning: Some of the branches in linux-next are still based on v5.12-rc1,
so please be careful if you are trying to bisect a bug.
News: if your -next included tree is based on Linus' tree tag
v5.12-rc1{,-dontuse} (or somewhere between v5.11 and that tag), please
consider rebasing it onto
Hi all,
News: this release includes the removal of 8 architectures ...
Changes since 20180314:
New tree: apparmor
The syscalls tree lost its build failures.
The asm-generic tree gained conflicts against the input-current, kbuild
and syscalls trees.
The nds32 tree gained a conflict against the
Hi all,
Please do not add any v4.7 related material to your linux-next included
trees until after v4.6-rc1 is released.
Changes since 20160314:
The net-next tree gained conflicts agains Linus' tree.
The tip tree gained conflicts against the pm tree.
The aio tree regained its build failure for
Hi all,
Changes since 20130314:
The l2-mtd tree gained conflicts against the mtd tree.
The staging tree gained a conflict against Linus' tree.
The gpio tree still had its build failure for which I reverted a commit.
6 matches
Mail list logo