linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Joonsoo Kim" <iamjoonsoo.kim@lge.com>
To: 'Mark Brown' <broonie@kernel.org>,
	'Andrew Morton' <akpm@linux-foundation.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>
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)
Date: Tue, 8 Mar 2016 15:25:46 +0900	[thread overview]
Message-ID: <002b01d17903$59b2ae00$0d180a00$@lge.com> (raw)
In-Reply-To: <20160308022056.GV18327@sirena.org.uk>



> -----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.

Thanks.

  reply	other threads:[~2016-03-08  6:25 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 [this message]
2016-03-08  6:32     ` Andrew Morton

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='002b01d17903$59b2ae00$0d180a00$@lge.com' \
    --to=iamjoonsoo.kim@lge.com \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=kernel-build-reports@lists.linaro.org \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mgorman@techsingularity.net \
    --cc=mina86@mina86.com \
    --cc=minchan@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=sergey.senozhatsky.work@gmail.com \
    --cc=will.deacon@arm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).