Re: linux-next: build failure after merge of the akpm-current tree

From	Stephen Rothwell <sfr@canb.auug.org.au>
Newsgroups	linux.kernel
Subject	Re: linux-next: build failure after merge of the akpm-current tree
Date	2017-06-15 04:10 +0200
Message-ID	<tSsop-4ML-1@gated-at.bofh.it> (permalink)
References	<tOUjg-8cR-17@gated-at.bofh.it> <tSrVn-4m9-5@gated-at.bofh.it> <tSseJ-4tL-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

Hi Kees,

On Wed, 14 Jun 2017 18:56:30 -0700 Kees Cook <keescook@chromium.org> wrote:
>
> I sent a series for -mm (or maintainers) to merge that should catch
> everything. Do you want me to carry it in my kspp tree instead? (My
> original intention was to carry all the fixes and the fortify patch in
> kspp but akpm took it into -mm somewhat unexpectedly, not that I'm
> complaining.)

Andrew is currently not responding to stuff (he warned us last week),
so if you do put the series in your tree, I will remove it from my copy
of Andrew's quilt series.  All the fixes necessary to make this usable
should really be in the same tree if possible.

(I am assuming that the fix patches have been reviewed and acked by
appropriate people.)
-- 
Cheers,
Stephen Rothwell

Thread

Re: linux-next: build failure after merge of the akpm-current tree Stephen Rothwell <sfr@canb.auug.org.au> - 2017-06-15 03:40 +0200
  Re: linux-next: build failure after merge of the akpm-current tree Kees Cook <keescook@chromium.org> - 2017-06-15 04:00 +0200
    Re: linux-next: build failure after merge of the akpm-current tree Daniel Micay <danielmicay@gmail.com> - 2017-06-15 04:00 +0200
      Re: linux-next: build failure after merge of the akpm-current tree Stephen Rothwell <sfr@canb.auug.org.au> - 2017-06-15 04:10 +0200
        Re: linux-next: build failure after merge of the akpm-current tree Daniel Micay <danielmicay@gmail.com> - 2017-06-15 04:20 +0200
          Re: linux-next: build failure after merge of the akpm-current tree Kees Cook <keescook@chromium.org> - 2017-06-15 04:30 +0200
            Re: linux-next: build failure after merge of the akpm-current tree Daniel Micay <danielmicay@gmail.com> - 2017-06-15 04:40 +0200
    Re: linux-next: build failure after merge of the akpm-current tree Stephen Rothwell <sfr@canb.auug.org.au> - 2017-06-15 04:10 +0200
      Re: linux-next: build failure after merge of the akpm-current tree Kees Cook <keescook@chromium.org> - 2017-06-15 04:20 +0200
        Re: linux-next: build failure after merge of the akpm-current tree Daniel Micay <danielmicay@gmail.com> - 2017-06-15 05:20 +0200
          Re: linux-next: build failure after merge of the akpm-current tree Michael Ellerman <mpe@ellerman.id.au> - 2017-06-15 08:00 +0200
            Re: linux-next: build failure after merge of the akpm-current tree Kees Cook <keescook@chromium.org> - 2017-06-15 17:20 +0200
    Re: linux-next: build failure after merge of the akpm-current tree Andrew Morton <akpm@linux-foundation.org> - 2017-06-15 21:20 +0200
      Re: linux-next: build failure after merge of the akpm-current tree Kees Cook <keescook@chromium.org> - 2017-06-16 01:50 +0200
        Re: linux-next: build failure after merge of the akpm-current tree Daniel Micay <danielmicay@gmail.com> - 2017-06-16 02:10 +0200
          Re: linux-next: build failure after merge of the akpm-current tree Kees Cook <keescook@chromium.org> - 2017-06-16 02:40 +0200
            Re: linux-next: build failure after merge of the akpm-current tree Stephen Rothwell <sfr@canb.auug.org.au> - 2017-06-16 03:30 +0200
        Re: linux-next: build failure after merge of the akpm-current tree Andrew Morton <akpm@linux-foundation.org> - 2017-06-16 19:20 +0200
          Re: linux-next: build failure after merge of the akpm-current tree Kees Cook <keescook@chromium.org> - 2017-06-19 22:30 +0200

csiph-web