Hi all,
Changes since 20210204:
The pm tree gained build failures so I used the version from
next-20210204.
The net-next tree still had its build failure so I applied supplied
patches.
The amdgpu tree gained a build failure due to an interaction with the
drm tree for which I reverted a commit
On Tue, Feb 05, 2019 at 09:40:40AM -0800, Randy Dunlap wrote:
> On 2/4/19 10:12 PM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20190204:
> >
>
> on i386:
>
> ../fs/btrfs/zstd.c: In function ‘zstd_reclaim_timer_fn’:
> ../fs/btrfs/zstd.c:27:35: warning: integer overflow in
On 2/4/19 10:12 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20190204:
>
on i386:
../fs/btrfs/zstd.c: In function ‘zstd_reclaim_timer_fn’:
../fs/btrfs/zstd.c:27:35: warning: integer overflow in expression [-Woverflow]
#define ZSTD_BTRFS_RECLAIM_NS (45 * NSEC_PER_SEC)
Hi all,
Changes since 20190204:
The vfs tree lost its build failure.
The net-next tree lost its build failure.
The drm-tegra tree lost its build failure.
The akpm-current tree gained a conflict against the net tree.
Non-merge commits (relative to Linus' tree): 5606
6290 files changed,
Hi all,
Please do not add any v4.17 material to your linux-next included branches
until after v4.16-rc1 has been released.
Changes since 20180202:
Linus' tree gained a build failure for which I applied a fix.
The kvm tree gained conflicts against Linus' tree.
Non-merge commits (relative to
Hi all,
Please do not add any v4.17 material to your linux-next included branches
until after v4.16-rc1 has been released.
Changes since 20180202:
Linus' tree gained a build failure for which I applied a fix.
The kvm tree gained conflicts against Linus' tree.
Non-merge commits (relative to
Hi all,
Changes since 20160204:
The sunxi tree gained a build failure so I used the version from
next-20160204.
The gpio tree still had its build failure so I used the version from
next-20160128.
The aio tree still had a build failure so I used the version from
next-20160111.
Non-merge
Hi all,
Changes since 20160204:
The sunxi tree gained a build failure so I used the version from
next-20160204.
The gpio tree still had its build failure so I used the version from
next-20160128.
The aio tree still had a build failure so I used the version from
next-20160111.
Non-merge
Hi all,
This tree fails (more than usual) the powerpc allyesconfig build.
Changes since 20140204:
Removed tree: init (submitted and done with)
Undropped tree: parisc-hd
The parisc-hd tree lost its conflicts and so is back.
The powerpc tree still had its build failure.
Non-merge commits
Hi all,
This tree fails (more than usual) the powerpc allyesconfig build.
Changes since 20140204:
Removed tree: init (submitted and done with)
Undropped tree: parisc-hd
The parisc-hd tree lost its conflicts and so is back.
The powerpc tree still had its build failure.
Non-merge commits
On Tue, Feb 5, 2013 at 6:34 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20130204:
>
> The powerpc tree still had a build failure.
>
> The nfsd tree lost its build.
>
> The sound-asoc tree gained a build failure so I used the version from
> next-20130204.
>
Several people ask for
On Tue, Feb 5, 2013 at 6:34 AM, Stephen Rothwell s...@canb.auug.org.au wrote:
Hi all,
Changes since 20130204:
The powerpc tree still had a build failure.
The nfsd tree lost its build.
The sound-asoc tree gained a build failure so I used the version from
next-20130204.
Several people
Hi all,
Changes since 20130204:
The powerpc tree still had a build failure.
The nfsd tree lost its build.
The sound-asoc tree gained a build failure so I used the version from
next-20130204.
I have created today's
Hi all,
Changes since 20130204:
The powerpc tree still had a build failure.
The nfsd tree lost its build.
The sound-asoc tree gained a build failure so I used the version from
next-20130204.
I have created today's
14 matches
Mail list logo
