From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kbuild test robot <fengguang.wu@intel.com>,
kbuild-all@01.org, linux-kernel@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>,
Linux Memory Management List <linux-mm@kvack.org>,
Chris Metcalf <cmetcalf@mellanox.com>
Subject: Re: undefined reference to `early_panic'
Date: Tue, 7 Jun 2016 09:31:17 +1000 [thread overview]
Message-ID: <20160607093117.541bed6a@canb.auug.org.au> (raw)
In-Reply-To: <20160606133120.cb13d4fa3b6bba4f5b427ca5@linux-foundation.org>
Hi Andrew,
On Mon, 6 Jun 2016 13:31:20 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
>
> From: Andrew Morton <akpm@linux-foundation.org>
> Subject: tile: early_printk.o is always required
Added to linux-next today (will be dropped if it turns up elsewhere).
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2016-06-06 23:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-05 4:33 undefined reference to `early_panic' kbuild test robot
2016-06-06 20:31 ` Andrew Morton
2016-06-06 20:36 ` Chris Metcalf
2016-06-06 23:31 ` Stephen Rothwell [this message]
2016-06-07 9:17 ` tile: early_printk.o is always required kbuild test robot
2016-06-07 19:52 ` Andrew Morton
2016-06-07 20:56 ` [PATCH] tile: allow disabling CONFIG_EARLY_PRINTK Chris Metcalf
-- strict thread matches above, loose matches on Subject: below --
2016-04-17 13:57 undefined reference to `early_panic' kbuild test robot
2016-04-03 5:59 kbuild test robot
2016-03-21 6:57 kbuild test robot
2016-03-13 14:37 kbuild test robot
2016-02-28 12:18 kbuild test robot
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=20160607093117.541bed6a@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=cmetcalf@mellanox.com \
--cc=dan.j.williams@intel.com \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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).