From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Dirk Brandewie <dirk.j.brandewie@intel.com>
Subject: Re: linux-next: Tree for Feb 11 (intel_pstate.c)
Date: Mon, 11 Feb 2013 08:18:15 -0800 [thread overview]
Message-ID: <511919C7.5080502@infradead.org> (raw)
In-Reply-To: <20130211184749.565d8e47788f8be8aec1591f@canb.auug.org.au>
On 02/10/13 23:47, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20130208:
>
on i386:
drivers/built-in.o: In function `intel_pstate_timer_func':
intel_pstate.c:(.text+0x4ce97e): undefined reference to `__udivdi3'
drivers/built-in.o: In function `intel_pstate_cpu_init':
intel_pstate.c:(.cpuinit.text+0x974): undefined reference to `__udivdi3'
--
~Randy
next prev parent reply other threads:[~2013-02-11 16:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 7:47 linux-next: Tree for Feb 11 Stephen Rothwell
2013-02-11 16:18 ` Randy Dunlap [this message]
2013-02-11 17:29 ` linux-next: Tree for Feb 11 (intel_pstate.c) Dirk Brandewie
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=511919C7.5080502@infradead.org \
--to=rdunlap@infradead.org \
--cc=dirk.j.brandewie@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox