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,
Steven Miao <realmz6@gmail.com>,
Chris Metcalf <cmetcalf@ezchip.com>,
adi-buildroot-devel@lists.sourceforge.net
Subject: Re: linux-next: Tree for Feb 8
Date: Mon, 8 Feb 2016 17:26:11 +0530 [thread overview]
Message-ID: <20160208115611.GA10929@sudip-pc> (raw)
In-Reply-To: <20160208161756.6809f31a@canb.auug.org.au>
On Mon, Feb 08, 2016 at 04:17:56PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20160205:
My blackfin defconfig build fails with:
kallsyms failure: relative symbol value 0xffa00000 out of range in
relative mode
build log at:
https://travis-ci.org/sudipm-mukherjee/parport/jobs/107707060
and tilegx defconfig fails with:
kallsyms failure: relative symbol value 0xfffffff700020000 out of range
in relative mode
build log at:
https://travis-ci.org/sudipm-mukherjee/parport/jobs/107707069
I will do a bisect later today to see which has caused this.
regards
sudip
next prev parent reply other threads:[~2016-02-08 11:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 5:17 linux-next: Tree for Feb 8 Stephen Rothwell
2016-02-08 11:56 ` Sudip Mukherjee [this message]
2016-02-08 14:43 ` Sudip Mukherjee
2016-02-08 14:51 ` Ard Biesheuvel
2016-02-08 16:32 ` linux-next: Tree for Feb 8 (kernel/memremap.c, PRINTK, WARN) Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2024-02-08 3:55 linux-next: Tree for Feb 8 Stephen Rothwell
2023-02-08 3:31 Stephen Rothwell
2022-02-08 5:33 Stephen Rothwell
2021-02-08 12:52 Stephen Rothwell
2019-02-08 10:26 Stephen Rothwell
2018-02-08 3:07 Stephen Rothwell
2017-02-08 7:40 Stephen Rothwell
2013-02-08 4:31 Stephen Rothwell
2013-02-08 4:31 ` Stephen Rothwell
2012-02-08 5:16 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=20160208115611.GA10929@sudip-pc \
--to=sudipm.mukherjee@gmail.com \
--cc=adi-buildroot-devel@lists.sourceforge.net \
--cc=cmetcalf@ezchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=realmz6@gmail.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.