linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vishnu Sankar <vishnuocv@gmail.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: bentiss@kernel.org, linux-input@vger.kernel.org,
	 linux-kernel@vger.kernel.org, mpearson-lenovo@squebb.ca,
	 Vishnu Sankar <vsankar@lenovo.com>,
	kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] HID: lenovo: Fix to ensure the data as __le32 instead of u32
Date: Wed, 5 Mar 2025 09:08:04 +0900	[thread overview]
Message-ID: <CABxCQKuxA84swVQ50J7QCwR+raWP=9a73db6uenUnBVxc3O2+g@mail.gmail.com> (raw)
In-Reply-To: <n82p6032-740p-0o56-n808-99n5rpn9no23@xreary.bet>

Thank you Jiri.

On Wed, Mar 5, 2025 at 5:13 AM Jiri Kosina <jikos@kernel.org> wrote:
>
> On Tue, 14 Jan 2025, Vishnu Sankar wrote:
>
> > Ensure that data is treated as __le32 instead of u32 before
> > applying le32_to_cpu.
> > This patch fixes the sparse warning "sparse: cast to restricted __le32".
> >
> > Signed-off-by: Vishnu Sankar <vishnuocv@gmail.com>
> > Signed-off-by: Vishnu Sankar <vsankar@lenovo.com>
> > Reported-by: kernel test robot <lkp@intel.com>
> > Closes: https://lore.kernel.org/oe-kbuild-all/202501101635.qJrwAOwf-lkp@intel.com/
>
> Sorry for the delay, this fell in between cracks. Now applied.
>
> --
> Jiri Kosina
> SUSE Labs
>


-- 

Regards,

      Vishnu Sankar
     +817015150407 (Japan)

      reply	other threads:[~2025-03-05  0:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-14  0:41 [PATCH] HID: lenovo: Fix to ensure the data as __le32 instead of u32 Vishnu Sankar
2025-03-04 20:13 ` Jiri Kosina
2025-03-05  0:08   ` Vishnu Sankar [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='CABxCQKuxA84swVQ50J7QCwR+raWP=9a73db6uenUnBVxc3O2+g@mail.gmail.com' \
    --to=vishnuocv@gmail.com \
    --cc=bentiss@kernel.org \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mpearson-lenovo@squebb.ca \
    --cc=vsankar@lenovo.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).