From: Greg KH <gregkh@linuxfoundation.org>
To: Dawei Li <dawei.li@shingroup.cn>
Cc: arnd@arndb.de, fancer.lancer@gmail.com, lkp@intel.com,
linux-kernel@vger.kernel.org, set_pte_at@outlook.com,
stable@vger.kernel.org
Subject: Re: [PATCH] misc: eeprom/idt_89hpesx: Convert data structures to LE explicitly
Date: Tue, 30 Jan 2024 06:04:17 -0800 [thread overview]
Message-ID: <2024013039-asleep-rally-39c0@gregkh> (raw)
In-Reply-To: <20240130040632.3039911-1-dawei.li@shingroup.cn>
On Tue, Jan 30, 2024 at 12:06:32PM +0800, Dawei Li wrote:
> For data structures needs cpu_to_le* conversion, its prototype needs to
> be declared with __le* explicitly.
>
> Fixes: cfad6425382e ("eeprom: Add IDT 89HPESx EEPROM/CSR driver")
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202401261250.b07Yt30Z-lkp@intel.com/
> Signed-off-by: Dawei Li <dawei.li@shingroup.cn>
> Cc: <stable@vger.kernel.org>
> ---
> drivers/misc/eeprom/idt_89hpesx.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/misc/eeprom/idt_89hpesx.c b/drivers/misc/eeprom/idt_89hpesx.c
> index d807d08e2614..327afb866b21 100644
> --- a/drivers/misc/eeprom/idt_89hpesx.c
> +++ b/drivers/misc/eeprom/idt_89hpesx.c
> @@ -129,7 +129,7 @@ struct idt_smb_seq {
> struct idt_eeprom_seq {
> u8 cmd;
> u8 eeaddr;
> - u16 memaddr;
> + __le16 memaddr;
> u8 data;
> } __packed;
>
> @@ -141,8 +141,8 @@ struct idt_eeprom_seq {
> */
> struct idt_csr_seq {
> u8 cmd;
> - u16 csraddr;
> - u32 data;
> + __le16 csraddr;
> + __le32 data;
> } __packed;
>
> /*
Declaring them this way is nice, but this doesn't actually "fix"
anything at all as no code is actually changed.
So how is ths a bugfix? How does this patch do anything?
confused,
greg k-h
next prev parent reply other threads:[~2024-01-30 16:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 4:06 [PATCH] misc: eeprom/idt_89hpesx: Convert data structures to LE explicitly Dawei Li
2024-01-30 9:54 ` Serge Semin
2024-01-30 14:04 ` Greg KH [this message]
2024-01-31 1:34 ` Dawei Li
2024-01-31 2:07 ` Greg KH
2024-01-31 2:19 ` Dawei Li
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=2024013039-asleep-rally-39c0@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=dawei.li@shingroup.cn \
--cc=fancer.lancer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=set_pte_at@outlook.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.