From: Mark Brown <broonie@kernel•org>
To: Catalin Marinas <catalin.marinas@arm•com>
Cc: Andrew Morton <akpm@linux-foundation•org>,
"Kirill A. Shutemov" <kirill.shutemov@linux•intel.com>,
Toshi Kani <toshi.kani@hp•com>,
Matthew Wilcox <willy@linux•intel.com>,
Will Deacon <Will.Deacon@arm•com>,
"kernel-build-reports@lists•linaro.org"
<kernel-build-reports@lists•linaro.org>,
"linaro-kernel@lists•linaro.org" <linaro-kernel@lists•linaro.org>,
"linux-next@vger•kernel.org" <linux-next@vger•kernel.org>,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>
Subject: Re: next-20150716 build: 4 failures 88 warnings (next-20150716)
Date: Thu, 16 Jul 2015 15:01:46 +0100 [thread overview]
Message-ID: <20150716140146.GL4039@sirena.org.uk> (raw)
In-Reply-To: <20150716134836.GB26865@e104818-lin.cambridge.arm.com>
[-- Attachment #1: Type: text/plain, Size: 506 bytes --]
On Thu, Jul 16, 2015 at 02:48:36PM +0100, Catalin Marinas wrote:
> On Thu, Jul 16, 2015 at 02:41:52PM +0100, Mark Brown wrote:
> > The update_mmu_cache() function is defined unconditionally in
> > asm/tlbflush.h so there is presumably some path of conditional
> > inclusions which causes it not to get declared in an allnoconfig - I
> > didn't chase that down yet.
> Maybe we should move it to asm/pgtable.h like many other architectures.
Seems likely to be more robust in future if we're consistent...
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-07-16 14:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 10:05 next-20150716 build: 4 failures 88 warnings (next-20150716) Build bot for Mark Brown
2015-07-16 13:41 ` Mark Brown
2015-07-16 13:48 ` Catalin Marinas
2015-07-16 14:01 ` Mark Brown [this message]
2015-07-16 21:29 ` Andrew Morton
2015-07-16 13:59 ` Mark Brown
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=20150716140146.GL4039@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=Will.Deacon@arm$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=catalin.marinas@arm$(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-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=toshi.kani@hp$(echo .)com \
--cc=willy@linux$(echo .)intel.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