From: Andrew Morton <akpm@linux-foundation•org>
To: Joonsoo Kim <iamjoonsoo.kim@lge•com>
Cc: 'Mark Brown' <broonie@kernel•org>,
'Michal Nazarewicz' <mina86@mina86•com>,
'Steven Rostedt' <rostedt@goodmis•org>,
'Mel Gorman' <mgorman@techsingularity•net>,
'Minchan Kim' <minchan@kernel•org>,
'Sergey Senozhatsky' <sergey.senozhatsky.work@gmail•com>,
"'Kirill A. Shutemov'" <kirill.shutemov@linux•intel.com>,
'Catalin Marinas' <catalin.marinas@arm•com>,
'Will Deacon' <will.deacon@arm•com>,
kernel-build-reports@lists•linaro.org,
linaro-kernel@lists•linaro.org, linux-next@vger•kernel.org,
linux-arm-kernel@lists•infradead.org
Subject: Re: next-20160307 build: 2 failures 19 warnings (next-20160307)
Date: Mon, 7 Mar 2016 22:32:01 -0800 [thread overview]
Message-ID: <20160307223201.06f055f4.akpm@linux-foundation.org> (raw)
In-Reply-To: <002b01d17903$59b2ae00$0d180a00$@lge.com>
On Tue, 8 Mar 2016 15:25:46 +0900 "Joonsoo Kim" <iamjoonsoo.kim@lge•com> wrote:
>
>
> > -----Original Message-----
> > From: Mark Brown [mailto:broonie@kernel•org]
> > Sent: Tuesday, March 08, 2016 11:21 AM
> > To: Andrew Morton; Joonsoo Kim; Michal Nazarewicz; Steven Rostedt; Mel
> > Gorman; Minchan Kim; Sergey Senozhatsky; Kirill A. Shutemov; Catalin
> > Marinas; Will Deacon
> > Cc: kernel-build-reports@lists•linaro.org; linaro-kernel@lists•linaro.org;
> > linux-next@vger•kernel.org; linux-arm-kernel@lists•infradead.org
> > Subject: Re: next-20160307 build: 2 failures 19 warnings (next-20160307)
> >
> > On Mon, Mar 07, 2016 at 11:38:44AM +0000, Build bot for Mark Brown wrote:
> >
> > For the past week or so an arm64 allmodconfig has failed to build. I've
> > not been able to perform a bisect to identify where as I've been
> > travelling but the errors are below, I suspect they are triggered by
> > recent changes in the akpm tree adding tracepoints to the page reference
> > code.
>
> Hello,
>
> It's already reported problem and solved by following patch.
>
> http://ozlabs.org/~akpm/mmots/broken-out/mm-page_ref-add-tracepoint-to-track
> -down-page-reference-manipulation-fix-3.patch
>
> Once Andrew releases new mmotm and it is applied to linux-next,
> no error will happen.
Yes, sorry, I have been remiss in cc'ing Stephen on things like this :(
prev parent reply other threads:[~2016-03-08 6:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 11:38 next-20160307 build: 2 failures 19 warnings (next-20160307) Build bot for Mark Brown
2016-03-08 2:20 ` Mark Brown
2016-03-08 6:25 ` Joonsoo Kim
2016-03-08 6:32 ` Andrew Morton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160307223201.06f055f4.akpm@linux-foundation.org \
--to=akpm@linux-foundation$(echo .)org \
--cc=broonie@kernel$(echo .)org \
--cc=catalin.marinas@arm$(echo .)com \
--cc=iamjoonsoo.kim@lge$(echo .)com \
--cc=kernel-build-reports@lists$(echo .)linaro.org \
--cc=kirill.shutemov@linux$(echo .)intel.com \
--cc=linaro-kernel@lists$(echo .)linaro.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mgorman@techsingularity$(echo .)net \
--cc=mina86@mina86$(echo .)com \
--cc=minchan@kernel$(echo .)org \
--cc=rostedt@goodmis$(echo .)org \
--cc=sergey.senozhatsky.work@gmail$(echo .)com \
--cc=will.deacon@arm$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox