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>
Subject: drivers/greybus/gb-beagleplay.c:347:24: sparse: sparse: restricted __le16 degrades to integer
Date: Tue, 14 Nov 2023 15:54:26 +0800 [thread overview]
Message-ID: <202311072329.Xogj7hGW-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: be3ca57cfb777ad820c6659d52e60bbdd36bf5ff
commit: ec558bbfea671ac020a6dc6be8bf8f0ee556cce0 greybus: Add BeaglePlay Linux Driver
date: 11 days ago
config: x86_64-randconfig-122-20231107 (https://download.01.org/0day-ci/archive/20231107/202311072329.Xogj7hGW-lkp@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231107/202311072329.Xogj7hGW-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/202311072329.Xogj7hGW-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/greybus/gb-beagleplay.c:347:24: sparse: sparse: restricted __le16 degrades to integer
vim +347 drivers/greybus/gb-beagleplay.c
ec558bbfea671a Ayush Singh 2023-10-17 338
ec558bbfea671a Ayush Singh 2023-10-17 339 static int gb_message_send(struct gb_host_device *hd, u16 cport, struct gb_message *msg, gfp_t mask)
ec558bbfea671a Ayush Singh 2023-10-17 340 {
ec558bbfea671a Ayush Singh 2023-10-17 341 struct gb_beagleplay *bg = dev_get_drvdata(&hd->dev);
ec558bbfea671a Ayush Singh 2023-10-17 342 struct hdlc_payload payloads[2];
ec558bbfea671a Ayush Singh 2023-10-17 343
ec558bbfea671a Ayush Singh 2023-10-17 344 dev_dbg(&hd->dev, "Sending greybus message with Operation %u, Type: %X on Cport %u",
ec558bbfea671a Ayush Singh 2023-10-17 345 msg->header->operation_id, msg->header->type, cport);
ec558bbfea671a Ayush Singh 2023-10-17 346
ec558bbfea671a Ayush Singh 2023-10-17 @347 if (msg->header->size > RX_HDLC_PAYLOAD)
ec558bbfea671a Ayush Singh 2023-10-17 348 return dev_err_probe(&hd->dev, -E2BIG, "Greybus message too big");
ec558bbfea671a Ayush Singh 2023-10-17 349
ec558bbfea671a Ayush Singh 2023-10-17 350 memcpy(msg->header->pad, &cport, sizeof(cport));
ec558bbfea671a Ayush Singh 2023-10-17 351
ec558bbfea671a Ayush Singh 2023-10-17 352 payloads[0].buf = msg->header;
ec558bbfea671a Ayush Singh 2023-10-17 353 payloads[0].len = sizeof(*msg->header);
ec558bbfea671a Ayush Singh 2023-10-17 354 payloads[1].buf = msg->payload;
ec558bbfea671a Ayush Singh 2023-10-17 355 payloads[1].len = msg->payload_size;
ec558bbfea671a Ayush Singh 2023-10-17 356
ec558bbfea671a Ayush Singh 2023-10-17 357 hdlc_tx_frames(bg, ADDRESS_GREYBUS, 0x03, payloads, 2);
ec558bbfea671a Ayush Singh 2023-10-17 358 greybus_message_sent(bg->gb_hd, msg, 0);
ec558bbfea671a Ayush Singh 2023-10-17 359
ec558bbfea671a Ayush Singh 2023-10-17 360 return 0;
ec558bbfea671a Ayush Singh 2023-10-17 361 }
ec558bbfea671a Ayush Singh 2023-10-17 362
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-11-14 7:59 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=202311072329.Xogj7hGW-lkp@intel.com \
--to=yujie.liu@intel.com \
--cc=ayushdevel1325@gmail.com \
--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®