From: Sudip Mukherjee <sudipm.mukherjee-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Kees Cook <keescook-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>,
Ard Biesheuvel
<ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
Russell King <rmk+kernel-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>
Cc: linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Stephen Rothwell <sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>,
kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: linux-next: Tree for Feb 12
Date: Fri, 12 Feb 2016 19:57:20 +0530 [thread overview]
Message-ID: <20160212142719.GA31729@sudip-pc> (raw)
In-Reply-To: <20160212162035.1e0260cd-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
On Fri, Feb 12, 2016 at 04:20:35PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20160211:
arm lpc18xx_defconfig build fails with the error:
./arch/arm/kernel/vmlinux.lds:702: undefined symbol `SECTION_SHIFT'
referenced in expression
bisect leads to:
64ac2e74f0b2 ("ARM: 8502/1: mm: mark section-aligned portion of rodata NX")
reverting that patch fixed the build.
build log at:
https://travis-ci.org/sudipm-mukherjee/parport/jobs/108716281
regards
sudip
next prev parent reply other threads:[~2016-02-12 14:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 5:20 linux-next: Tree for Feb 12 Stephen Rothwell
2016-02-12 6:02 ` Sudip Mukherjee
2016-02-13 7:49 ` Guenter Roeck
2016-02-13 14:57 ` Andy Lutomirski
2016-02-13 15:50 ` Borislav Petkov
2016-02-13 18:55 ` Sudip Mukherjee
[not found] ` <20160212162035.1e0260cd-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2016-02-12 14:27 ` Sudip Mukherjee [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-12 5:33 Stephen Rothwell
2024-02-12 4:31 Stephen Rothwell
2021-02-12 11:07 Stephen Rothwell
2020-02-12 2:58 Stephen Rothwell
2019-02-12 6:50 Stephen Rothwell
2018-02-12 2:46 Stephen Rothwell
2015-02-12 6:07 Stephen Rothwell
2014-02-12 5:47 Stephen Rothwell
2013-02-12 5:09 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=20160212142719.GA31729@sudip-pc \
--to=sudipm.mukherjee-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=keescook-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rmk+kernel-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org \
--cc=sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org \
/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).