From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Wentong Wu <wentong.wu@intel.com>
Cc: tomas.winkler@intel.com, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Jason Chen <jason.z.chen@intel.com>
Subject: Re: [PATCH 3/6] mei: vsc: Enhance SPI transfer of IVSC rom
Date: Sun, 23 Jun 2024 10:09:27 +0000 [thread overview]
Message-ID: <Znf0V9roQaUDu7_b@kekkonen.localdomain> (raw)
In-Reply-To: <20240623093056.4169438-4-wentong.wu@intel.com>
Hi Wentong,
On Sun, Jun 23, 2024 at 05:30:53PM +0800, Wentong Wu wrote:
> Constructing the SPI transfer command as per the specific request.
>
> Fixes: 566f5ca97680 ("mei: Add transport driver for IVSC device")
> Cc: stable@vger.kernel.org # for 6.8+
> Signed-off-by: Wentong Wu <wentong.wu@intel.com>
> Tested-by: Jason Chen <jason.z.chen@intel.com>
> ---
> drivers/misc/mei/vsc-tp.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/misc/mei/vsc-tp.c b/drivers/misc/mei/vsc-tp.c
> index 4595b1a25536..7a89e4e5d553 100644
> --- a/drivers/misc/mei/vsc-tp.c
> +++ b/drivers/misc/mei/vsc-tp.c
> @@ -331,7 +331,7 @@ int vsc_tp_rom_xfer(struct vsc_tp *tp, const void *obuf, void *ibuf, size_t len)
> return ret;
> }
>
> - ret = vsc_tp_dev_xfer(tp, tp->tx_buf, tp->rx_buf, len);
> + ret = vsc_tp_dev_xfer(tp, tp->tx_buf, ibuf ? tp->rx_buf : ibuf, len);
Is this correct? I.e. use ibuf when it's NULL, otherwise use tp->rx_buf?
> if (ret)
> return ret;
>
--
Kind regards,
Sakari Ailus
next prev parent reply other threads:[~2024-06-23 10:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-23 9:30 [PATCH 0/6] Fix MEI command timeout issue following warm reboot Wentong Wu
2024-06-23 9:30 ` [PATCH 1/6] mei: vsc: Enhance IVSC chipset reset toggling Wentong Wu
2024-06-23 10:06 ` Sakari Ailus
2024-06-23 10:48 ` Wu, Wentong
2024-06-23 9:30 ` [PATCH 2/6] mei: vsc: Enhance IVSC chipset stability during warm reboot Wentong Wu
2024-06-23 9:30 ` [PATCH 3/6] mei: vsc: Enhance SPI transfer of IVSC rom Wentong Wu
2024-06-23 10:09 ` Sakari Ailus [this message]
2024-06-23 10:42 ` Wu, Wentong
2024-06-23 9:30 ` [PATCH 4/6] mei: vsc: Utilize the appropriate byte order swap function Wentong Wu
2024-06-23 9:30 ` [PATCH 5/6] mei: vsc: Prevent timeout error with added delay post-firmware download Wentong Wu
2024-06-23 9:30 ` [PATCH 6/6] mei: vsc: Fix spelling error Wentong Wu
2024-06-23 10:08 ` Sakari Ailus
2024-06-23 10:30 ` Wu, Wentong
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=Znf0V9roQaUDu7_b@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jason.z.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tomas.winkler@intel.com \
--cc=wentong.wu@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
all inboxes | Powered by JetHome®