From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Alexander Usyskin <alexander.usyskin@intel.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Badal Nilawar <badal.nilawar@intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-kernel@vger.kernel.org,
Menachem Adin <menachem.adin@intel.com>,
stable@vger.kernel.org, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH char-misc v2] mei: lb: fix incorrect type in assignment
Date: Mon, 6 Jul 2026 16:32:43 +0200 [thread overview]
Message-ID: <2026070608-reformat-pungent-aeb4@gregkh> (raw)
In-Reply-To: <20260706-fix_type_le-v2-1-586826351454@intel.com>
On Mon, Jul 06, 2026 at 04:01:30PM +0300, Alexander Usyskin wrote:
> Fix the mix between __le32 and integer by casting
> the MEI_LB2_CMD constant as __le32 while using it.
>
> Fixes sparse waring:
> drivers/misc/mei/mei_lb.c:284:32: sparse: sparse: restricted __le32 degrades to integer
> drivers/misc/mei/mei_lb.c:330:40: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted __le32 [usertype] command_id @@ got int @@
> drivers/misc/mei/mei_lb.c:330:40: sparse: expected restricted __le32 [usertype] command_id
> drivers/misc/mei/mei_lb.c:330:40: sparse: got int
>
> Cc: stable@vger.kernel.org
Why cc: stable? It doesn't actually cause any functional change to the
code at all, right? This isn't running on s390, or am I mistaken?
thanks,
greg k-h
next prev parent reply other threads:[~2026-07-06 14:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 13:01 [PATCH char-misc v2] mei: lb: fix incorrect type in assignment Alexander Usyskin
2026-07-06 14:32 ` Greg Kroah-Hartman [this message]
2026-07-07 6:43 ` Usyskin, Alexander
2026-07-07 7:21 ` Andy Shevchenko
2026-07-07 8:47 ` Greg Kroah-Hartman
2026-07-07 9:02 ` Andy Shevchenko
2026-07-07 11:33 ` Usyskin, Alexander
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=2026070608-reformat-pungent-aeb4@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=alexander.usyskin@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=badal.nilawar@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=menachem.adin@intel.com \
--cc=stable@vger.kernel.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 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.