From: Linus Torvalds
> Sent: 26 August 2018 22:49
>
> So two weeks have passed, and the merge window for 4.19 is over.
>
> This was a fairly frustrating merge window, partly because 4.19 looks
> to be a pretty big release (no single reason), and partly just due to
> random noise.
...
Time for
From: Linus Torvalds
> Sent: 26 August 2018 22:49
>
> So two weeks have passed, and the merge window for 4.19 is over.
>
> This was a fairly frustrating merge window, partly because 4.19 looks
> to be a pretty big release (no single reason), and partly just due to
> random noise.
...
Time for
On Mon, Aug 27, 2018 at 02:56:32PM -0700, Linus Torvalds wrote:
> On Mon, Aug 27, 2018 at 6:45 AM Guenter Roeck wrote:
> >
> > Build results:
> > total: 132 pass: 129 fail: 3
>
> Thanks for running these. Looks like everything but the sparc thing is
> under control, and the sparc thing
On Mon, Aug 27, 2018 at 02:56:32PM -0700, Linus Torvalds wrote:
> On Mon, Aug 27, 2018 at 6:45 AM Guenter Roeck wrote:
> >
> > Build results:
> > total: 132 pass: 129 fail: 3
>
> Thanks for running these. Looks like everything but the sparc thing is
> under control, and the sparc thing
On Mon, Aug 27, 2018 at 6:45 AM Guenter Roeck wrote:
>
> Build results:
> total: 132 pass: 129 fail: 3
Thanks for running these. Looks like everything but the sparc thing is
under control, and the sparc thing might be one of those "big builds
don't work on sparc" ;(
Linus
On Mon, Aug 27, 2018 at 6:45 AM Guenter Roeck wrote:
>
> Build results:
> total: 132 pass: 129 fail: 3
Thanks for running these. Looks like everything but the sparc thing is
under control, and the sparc thing might be one of those "big builds
don't work on sparc" ;(
Linus
On Mon, 27 Aug 2018 06:44:59 PDT (-0700), li...@roeck-us.net wrote:
On Sun, Aug 26, 2018 at 02:49:14PM -0700, Linus Torvalds wrote:
So two weeks have passed, and the merge window for 4.19 is over.
[ ... ]
Anyway, go forth and test,
Build results:
total: 132 pass: 129 fail: 3
On Mon, 27 Aug 2018 06:44:59 PDT (-0700), li...@roeck-us.net wrote:
On Sun, Aug 26, 2018 at 02:49:14PM -0700, Linus Torvalds wrote:
So two weeks have passed, and the merge window for 4.19 is over.
[ ... ]
Anyway, go forth and test,
Build results:
total: 132 pass: 129 fail: 3
>
> On Sun, Aug 26, 2018 at 3:51 PM Linus Torvalds foundation.org> wrote:
> >
> > So two weeks have passed, and the merge window for 4.19 is over.
> >
>
>
> > Anyway, go forth and test,
> >
>
> I am seeing the errors use-after-free errors in mei_cl_write. dmesg as
> follows.
> Adding Tomas
>
> On Sun, Aug 26, 2018 at 3:51 PM Linus Torvalds foundation.org> wrote:
> >
> > So two weeks have passed, and the merge window for 4.19 is over.
> >
>
>
> > Anyway, go forth and test,
> >
>
> I am seeing the errors use-after-free errors in mei_cl_write. dmesg as
> follows.
> Adding Tomas
On Mon, Aug 27, 2018 at 11:13:11AM -0700, Christoph Hellwig wrote:
> On Mon, Aug 27, 2018 at 10:11:52AM -0700, Guenter Roeck wrote:
> > When building sparc32 images, this results in the following
> > error.
> >
> > drivers/base/platform.c: In function 'setup_pdev_archdata':
> >
On Mon, Aug 27, 2018 at 11:13:11AM -0700, Christoph Hellwig wrote:
> On Mon, Aug 27, 2018 at 10:11:52AM -0700, Guenter Roeck wrote:
> > When building sparc32 images, this results in the following
> > error.
> >
> > drivers/base/platform.c: In function 'setup_pdev_archdata':
> >
On Sun, Aug 26, 2018 at 3:51 PM Linus Torvalds
wrote:
>
> So two weeks have passed, and the merge window for 4.19 is over.
>
> Anyway, go forth and test,
>
I am seeing the errors use-after-free errors in mei_cl_write. dmesg as follows.
Adding Tomas Winkler to the thread.
[ 12.602912] PM:
On Sun, Aug 26, 2018 at 3:51 PM Linus Torvalds
wrote:
>
> So two weeks have passed, and the merge window for 4.19 is over.
>
> Anyway, go forth and test,
>
I am seeing the errors use-after-free errors in mei_cl_write. dmesg as follows.
Adding Tomas Winkler to the thread.
[ 12.602912] PM:
On Mon, Aug 27, 2018 at 10:11:52AM -0700, Guenter Roeck wrote:
> When building sparc32 images, this results in the following
> error.
>
> drivers/base/platform.c: In function 'setup_pdev_archdata':
> drivers/base/platform.c:235:22: error: assignment from incompatible pointer
> type
On Mon, Aug 27, 2018 at 10:11:52AM -0700, Guenter Roeck wrote:
> When building sparc32 images, this results in the following
> error.
>
> drivers/base/platform.c: In function 'setup_pdev_archdata':
> drivers/base/platform.c:235:22: error: assignment from incompatible pointer
> type
On Mon, Aug 27, 2018 at 08:46:41AM -0700, Christoph Hellwig wrote:
> > sparc:
> >
> > WARNING: CPU: 0 PID: 1 at ./include/linux/dma-mapping.h:516
> > esp_sbus_probe+0x408/0x6e8
> > WARNING: CPU: 0 PID: 1 at ./include/linux/dma-mapping.h:516
> > sparc_lance_probe_one+0x428/0x4f
> >
> > Missing
On Mon, Aug 27, 2018 at 08:46:41AM -0700, Christoph Hellwig wrote:
> > sparc:
> >
> > WARNING: CPU: 0 PID: 1 at ./include/linux/dma-mapping.h:516
> > esp_sbus_probe+0x408/0x6e8
> > WARNING: CPU: 0 PID: 1 at ./include/linux/dma-mapping.h:516
> > sparc_lance_probe_one+0x428/0x4f
> >
> > Missing
> sparc:
>
> WARNING: CPU: 0 PID: 1 at ./include/linux/dma-mapping.h:516
> esp_sbus_probe+0x408/0x6e8
> WARNING: CPU: 0 PID: 1 at ./include/linux/dma-mapping.h:516
> sparc_lance_probe_one+0x428/0x4f
>
> Missing initialization of coherent_dma_mask in the respective drivers.
>
> ---
> Each
> sparc:
>
> WARNING: CPU: 0 PID: 1 at ./include/linux/dma-mapping.h:516
> esp_sbus_probe+0x408/0x6e8
> WARNING: CPU: 0 PID: 1 at ./include/linux/dma-mapping.h:516
> sparc_lance_probe_one+0x428/0x4f
>
> Missing initialization of coherent_dma_mask in the respective drivers.
>
> ---
> Each
On Sun, Aug 26, 2018 at 02:49:14PM -0700, Linus Torvalds wrote:
> So two weeks have passed, and the merge window for 4.19 is over.
>
[ ... ]
>
> Anyway, go forth and test,
>
Build results:
total: 132 pass: 129 fail: 3
Failed builds:
riscv:defconfig
riscv:allnoconfig
On Sun, Aug 26, 2018 at 02:49:14PM -0700, Linus Torvalds wrote:
> So two weeks have passed, and the merge window for 4.19 is over.
>
[ ... ]
>
> Anyway, go forth and test,
>
Build results:
total: 132 pass: 129 fail: 3
Failed builds:
riscv:defconfig
riscv:allnoconfig
Hi all,
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-20180813 was the first linux-next after
the merge window opened.)
Commits in v4.19-rc1 (relative to v4.18): 12317
Commits in next-20180813:
Hi all,
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-20180813 was the first linux-next after
the merge window opened.)
Commits in v4.19-rc1 (relative to v4.18): 12317
Commits in next-20180813:
So two weeks have passed, and the merge window for 4.19 is over.
This was a fairly frustrating merge window, partly because 4.19 looks
to be a pretty big release (no single reason), and partly just due to
random noise. We had the L1TF hw vulnerability disclosure early in the
merge window, which
So two weeks have passed, and the merge window for 4.19 is over.
This was a fairly frustrating merge window, partly because 4.19 looks
to be a pretty big release (no single reason), and partly just due to
random noise. We had the L1TF hw vulnerability disclosure early in the
merge window, which
Hi Linus,
Please pull the following Kselftest update for Linux 4.19-rc1
This Kselftest update for 4.19-rc1:
- adds cgroup core selftests
- fixes compile warnings in android ion test
- fixes to bugs in exclude and skip paths in vDSO test
- removes obsolete config options
- adds missing
Hi Linus,
Please pull the following Kselftest update for Linux 4.19-rc1
This Kselftest update for 4.19-rc1:
- adds cgroup core selftests
- fixes compile warnings in android ion test
- fixes to bugs in exclude and skip paths in vDSO test
- removes obsolete config options
- adds missing
28 matches
Mail list logo
