public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Cochran <richardcochran@gmail.com>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: David Howells <dhowells@redhat.com>,
	kbuild-all@01.org, linux-kernel@vger.kernel.org,
	Nicolas Pitre <nicolas.pitre@linaro.org>
Subject: Re: undefined reference to `pps_unregister_source'
Date: Mon, 2 Jan 2017 10:00:02 +0100	[thread overview]
Message-ID: <20170102090002.GA13610@localhost.localdomain> (raw)
In-Reply-To: <201701020058.NvBIXVL0%fengguang.wu@intel.com>

On Mon, Jan 02, 2017 at 12:22:01AM +0800, kbuild test robot wrote:
>    drivers/built-in.o: In function `ptp_clock_unregister':
> >> (.text+0x40e0a5): undefined reference to `pps_unregister_source'
>    drivers/built-in.o: In function `ptp_clock_unregister':
> >> (.text+0x40e0cc): undefined reference to `posix_clock_unregister'
>    drivers/built-in.o: In function `ptp_clock_event':
> >> (.text+0x40e249): undefined reference to `pps_event'
>    drivers/built-in.o: In function `ptp_clock_register':
> >> (.text+0x40e5e1): undefined reference to `pps_register_source'
>    drivers/built-in.o: In function `ptp_clock_register':
> >> (.text+0x40e62c): undefined reference to `posix_clock_register'
>    drivers/built-in.o: In function `ptp_clock_register':
>    (.text+0x40e68d): undefined reference to `pps_unregister_source'

Nicolas,

This looks like fallout from the posix timers tinification.
Can you please take a look at that config?

Thanks,
Richard

  reply	other threads:[~2017-01-02  9:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-01 16:22 undefined reference to `pps_unregister_source' kbuild test robot
2017-01-02  9:00 ` Richard Cochran [this message]
2017-01-03  2:59   ` Nicolas Pitre

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=20170102090002.GA13610@localhost.localdomain \
    --to=richardcochran@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=fengguang.wu@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas.pitre@linaro.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