From: Jiri Kosina <jikos@kernel.org>
To: Zhang Lixu <lixu.zhang@intel.com>
Cc: linux-input@vger.kernel.org, srinivas.pandruvada@linux.intel.com,
benjamin.tissoires@redhat.com
Subject: Re: [PATCH] HID: intel-ish-hid: Fix build error for COMPILE_TEST
Date: Thu, 23 May 2024 14:15:08 +0200 (CEST) [thread overview]
Message-ID: <nycvar.YFH.7.76.2405231413340.16865@cbobk.fhfr.pm> (raw)
In-Reply-To: <20240523011401.705577-1-lixu.zhang@intel.com>
On Thu, 23 May 2024, Zhang Lixu wrote:
> kernel test robot reported build error due to a pointer type mismatch:
>
> .../ishtp/loader.c:172:8: error: incompatible pointer types passing
> '__le64 *' (aka 'unsigned long long *') to parameter of type
> 'dma_addr_t *' (aka 'unsigned int *')
>
> The issue arises because the driver, which is primarily intended for
> x86-64, is also built for i386 when COMPILE_TEST is enabled.
>
> Resolve type mismatch by using a temporary dma_addr_t variable to hold
> the DMA address. Populate this temporary variable in dma_alloc_coherent()
> function, and then convert and store the address in the
> fragment->fragment_tbl[i].ddr_adrs field in the correct format.
> Similarly, convert the ddr_adrs field back to dma_addr_t when freeing
> the DMA buffer with dma_free_coherent().
>
> Fixes: 579a267e4617 ("HID: intel-ish-hid: Implement loading firmware from host feature")
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202405201313.SAStVPrT-lkp@intel.com/
> Signed-off-by: Zhang Lixu <lixu.zhang@intel.com>
Applied to hid.git#for-6.9/upstream-fixes.
Thanks,
--
Jiri Kosina
SUSE Labs
prev parent reply other threads:[~2024-05-23 12:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 1:14 [PATCH] HID: intel-ish-hid: Fix build error for COMPILE_TEST Zhang Lixu
2024-05-23 12:15 ` Jiri Kosina [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=nycvar.YFH.7.76.2405231413340.16865@cbobk.fhfr.pm \
--to=jikos@kernel.org \
--cc=benjamin.tissoires@redhat.com \
--cc=linux-input@vger.kernel.org \
--cc=lixu.zhang@intel.com \
--cc=srinivas.pandruvada@linux.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