From: Oliver Neukum <oneukum@suse.de>
To: Bastien Nocera <hadess@hadess.net>, kbuild test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, linux-usb@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [usb:usb-testing 18/18] drivers/usb/misc/apple-mfi-fastcharge.c:173:29: sparse: sparse: restricted __le16 degrades to integer
Date: Thu, 13 Feb 2020 11:37:47 +0100 [thread overview]
Message-ID: <1581590267.21415.12.camel@suse.de> (raw)
In-Reply-To: <034bc43c35a75a84787bc786c8694607552a8139.camel@hadess.net>
Am Donnerstag, den 13.02.2020, 09:56 +0100 schrieb Bastien Nocera:
>
> Is that something I should be fixing? I'm guessing that I just need to
> cast the constant side to a type the same size as those fields, but is
> that necessary?
Hi,
I am on it. Expect a patch in half an hour.
Regards
Oliver
prev parent reply other threads:[~2020-02-13 10:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 7:01 [usb:usb-testing 18/18] drivers/usb/misc/apple-mfi-fastcharge.c:173:29: sparse: sparse: restricted __le16 degrades to integer kbuild test robot
2020-02-13 8:56 ` Bastien Nocera
2020-02-13 10:37 ` Oliver Neukum [this message]
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=1581590267.21415.12.camel@suse.de \
--to=oneukum@suse.de \
--cc=gregkh@linuxfoundation.org \
--cc=hadess@hadess.net \
--cc=kbuild-all@lists.01.org \
--cc=linux-usb@vger.kernel.org \
--cc=lkp@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).