From: Richard Cochran <richardcochran@gmail.com>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: Raghu Vatsavayi <rvatsavayi@caviumnetworks.com>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: [PATCH] LiquidIO VF: s/select/imply/ for PTP_1588_CLOCK
Date: Tue, 3 Jan 2017 20:24:12 +0100 [thread overview]
Message-ID: <20170103192412.GA23297@netboy> (raw)
In-Reply-To: <alpine.LFD.2.20.1701031331450.21662@knanqh.ubzr>
On Tue, Jan 03, 2017 at 01:57:00PM -0500, Nicolas Pitre wrote:
> Fix a minor fallout from the merge of the timers and the networking
> trees. The following error may result if the PTP_1588_CLOCK
> prerequisites are not available:
>
> 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'
>
> Signed-off-by: Nicolas Pitre <nico@linaro.org>
Thanks for following up on this.
Acked-by: Richard Cochran <richardcochran@gmail.com>
next prev parent reply other threads:[~2017-01-03 19:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170103101105.GA24780@localhost.localdomain>
2017-01-03 18:57 ` [PATCH] LiquidIO VF: s/select/imply/ for PTP_1588_CLOCK Nicolas Pitre
2017-01-03 19:24 ` Richard Cochran [this message]
2017-01-04 18:27 ` David Miller
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=20170103192412.GA23297@netboy \
--to=richardcochran@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=nicolas.pitre@linaro.org \
--cc=rvatsavayi@caviumnetworks.com \
/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.