From: Fengguang Wu <fengguang.wu@intel.com>
To: Joe Perches <joe@perches.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: undefined reference to `printk'
Date: Mon, 26 Sep 2016 09:54:29 +0800 [thread overview]
Message-ID: <20160926015429.z5czauf5c5imnkse@wfg-t540p.sh.intel.com> (raw)
In-Reply-To: <1474775186.23838.23.camel@perches.com>
Hi Joe,
On Sat, Sep 24, 2016 at 08:46:26PM -0700, Joe Perches wrote:
>On Sun, 2016-09-25 at 11:40 +0800, kbuild test robot wrote:
>> Hi Joe,
>
>Hey Fengguang
>
>> It's probably a bug fix that unveils the link errors.
>
>I think all of these reports about compiler-gcc integrations
>are bogons.
Yes, sorry for the noises again!
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>> head: 9c0e28a7be656d737fb18998e2dcb0b8ce595643
>> commit: cb984d101b30eb7478d32df56a0023e4603cba7f compiler-gcc: integrate the various compiler-gcc[345].h files
It looks there are different commit SHA1 in different trees for that patch.
I'll match it by patch subject rather than commit id.
Cheers,
Fengguang
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-09-26 1:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-25 3:40 kbuild test robot
2016-09-25 3:46 ` Joe Perches
2016-09-26 1:54 ` Fengguang Wu [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-07-27 20:56 kbuild test robot
2016-07-19 9:10 kbuild test robot
2016-07-03 15:39 kbuild test robot
2016-06-26 1:19 kbuild test robot
2016-06-27 5:14 ` Yoshinori Sato
2016-06-12 2:17 kbuild test robot
2016-06-12 4:38 ` Josh Triplett
2016-06-27 5:26 ` Yoshinori Sato
2016-06-05 0:43 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=20160926015429.z5czauf5c5imnkse@wfg-t540p.sh.intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.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