From: kernel test robot <yujie.liu@intel.com>
To: Ayush Singh <ayushdevel1325@gmail.com>
Cc: <oe-kbuild-all@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Subject: drivers/greybus/gb-beagleplay.c:173: undefined reference to `crc_ccitt'
Date: Fri, 10 Nov 2023 13:49:41 +0800 [thread overview]
Message-ID: <202311100836.JBsBIf8t-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: a12deb44f9734dc25970c266249b272e44d3d1b5
commit: ec558bbfea671ac020a6dc6be8bf8f0ee556cce0 greybus: Add BeaglePlay Linux Driver
date: 2 weeks ago
config: x86_64-randconfig-011-20231110 (https://download.01.org/0day-ci/archive/20231110/202311100836.JBsBIf8t-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231110/202311100836.JBsBIf8t-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <yujie.liu@intel.com>
| Closes: https://lore.kernel.org/r/202311100836.JBsBIf8t-lkp@intel.com/
All errors (new ones prefixed by >>):
ld: vmlinux.o: in function `hdlc_append_tx_u8':
>> drivers/greybus/gb-beagleplay.c:173: undefined reference to `crc_ccitt'
>> ld: drivers/greybus/gb-beagleplay.c:173: undefined reference to `crc_ccitt'
>> ld: drivers/greybus/gb-beagleplay.c:173: undefined reference to `crc_ccitt'
ld: vmlinux.o: in function `hdlc_rx_frame':
drivers/greybus/gb-beagleplay.c:234: undefined reference to `crc_ccitt'
vim +173 drivers/greybus/gb-beagleplay.c
ec558bbfea671a Ayush Singh 2023-10-17 170
ec558bbfea671a Ayush Singh 2023-10-17 171 static void hdlc_append_tx_u8(struct gb_beagleplay *bg, u8 value)
ec558bbfea671a Ayush Singh 2023-10-17 172 {
ec558bbfea671a Ayush Singh 2023-10-17 @173 bg->tx_crc = crc_ccitt(bg->tx_crc, &value, 1);
ec558bbfea671a Ayush Singh 2023-10-17 174 hdlc_append_escaped(bg, value);
ec558bbfea671a Ayush Singh 2023-10-17 175 }
ec558bbfea671a Ayush Singh 2023-10-17 176
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-11-10 18:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202311100836.JBsBIf8t-lkp@intel.com \
--to=yujie.liu@intel.com \
--cc=ayushdevel1325@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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
all inboxes | Powered by JetHome®