From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Mark Rutland <mark.rutland@arm.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Jeremy Linton <jeremy.linton@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-arch@vger.kernel.org
Subject: Re: linux-next: Tree for Feb 9
Date: Tue, 9 Feb 2016 13:04:28 +0530 [thread overview]
Message-ID: <20160209073428.GA24863@sudip-pc> (raw)
In-Reply-To: <20160209164104.4ecaa0ce@canb.auug.org.au>
On Tue, Feb 09, 2016 at 04:41:04PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20160208:
tilepro, tilegx, mips defconfig build fails with the error:
../include/asm-generic/fixmap.h: In function '__set_fixmap_offset':
../include/asm-generic/fixmap.h:77:2: error: implicit declaration of
function '__set_fixmap' [-Werror=implicit-function-declaration]
caused by:
commit ac4c0ac73485 ("asm-generic: make __set_fixmap_offset a static inline")
Reverting the commit fixes the issue.
regards
sudip
next prev parent reply other threads:[~2016-02-09 7:34 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 5:41 linux-next: Tree for Feb 9 Stephen Rothwell
2016-02-09 7:34 ` Sudip Mukherjee [this message]
2016-02-09 12:00 ` Mark Rutland
2016-02-09 12:00 ` Mark Rutland
2016-02-09 12:00 ` Mark Rutland
2016-02-09 13:48 ` Geert Uytterhoeven
2016-02-09 14:35 ` Mark Rutland
2016-02-09 14:35 ` Mark Rutland
2016-02-09 14:35 ` Mark Rutland
2016-02-09 14:38 ` Catalin Marinas
2016-02-09 15:08 ` Arnd Bergmann
2016-02-09 16:01 ` Mark Rutland
2016-02-09 16:08 ` Arnd Bergmann
2016-02-09 16:13 ` [PATCH] asm-generic: Fix build when __set_fixmap is absent kbuild test robot
2016-02-09 16:33 ` Mark Rutland
2016-02-09 16:45 ` Arnd Bergmann
2016-02-09 16:52 ` Catalin Marinas
2016-02-09 17:21 ` Mark Rutland
2016-02-09 17:21 ` Mark Rutland
2016-02-09 17:21 ` Mark Rutland
2016-02-09 17:27 ` Catalin Marinas
-- strict thread matches above, loose matches on Subject: below --
2026-02-09 16:52 linux-next: Tree for Feb 9 Mark Brown
2024-02-09 5:09 Stephen Rothwell
2023-02-09 3:49 Stephen Rothwell
2022-02-09 5:52 Stephen Rothwell
2021-02-09 11:28 Stephen Rothwell
2018-02-09 2:54 Stephen Rothwell
2017-02-09 6:28 Stephen Rothwell
2015-02-09 10:18 Stephen Rothwell
2012-02-09 5:04 Stephen Rothwell
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=20160209073428.GA24863@sudip-pc \
--to=sudipm.mukherjee@gmail.com \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=jeremy.linton@arm.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.