From: "Arnd Bergmann" <arnd@arndb.de>
To: "Arnd Bergmann" <arnd@kernel.org>,
"srinivas.pandruvada@linux.intel.com"
<srinivas.pandruvada@linux.intel.com>,
"Jiri Kosina" <jikos@kernel.org>,
"Benjamin Tissoires" <bentiss@kernel.org>,
"Lixu Zhang" <lixu.zhang@intel.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] HID: intel-ish-hid: fix endian-conversion
Date: Tue, 28 May 2024 14:45:07 +0200 [thread overview]
Message-ID: <dd2a2483-0ad4-4563-8cc2-885a47a96e71@app.fastmail.com> (raw)
In-Reply-To: <20240528115802.3122955-2-arnd@kernel.org>
On Tue, May 28, 2024, at 13:57, Arnd Bergmann wrote:
>
> for (i = 0; i < fragment->fragment_cnt && offset < ish_fw->size; i++)
> {
> dma_bufs[i] = dma_alloc_coherent(dev->devc, fragment_size,
> &dma_addr, GFP_KERNEL);
> + dma_bufs[i] = dma_alloc_coherent(dev->devc, fragment_size,
> + &dma, GFP_KERNEL);
> if (!dma_bufs[i])
> return -ENOMEM;
>
Sorry about this one, the duplicate linen was an incorrect
rebase. I've fixed this one locally but did not resend the
series since I'm still waiting for other review comments.
Arnd
next prev parent reply other threads:[~2024-05-28 12:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 11:57 [PATCH 1/2] HID: intel-ish-hid: fix cache management mistake Arnd Bergmann
2024-05-28 11:57 ` [PATCH 2/2] HID: intel-ish-hid: fix endian-conversion Arnd Bergmann
2024-05-28 12:45 ` Arnd Bergmann [this message]
2024-05-28 21:06 ` kernel test robot
2024-05-28 21:17 ` kernel test robot
2024-05-29 7:05 ` Zhang, Lixu
2024-05-29 13:18 ` Arnd Bergmann
2024-05-31 3:49 ` srinivas pandruvada
2024-05-31 16:29 ` Arnd Bergmann
2024-05-29 6:46 ` [PATCH 1/2] HID: intel-ish-hid: fix cache management mistake Zhang, Lixu
2024-05-29 7:06 ` Arnd Bergmann
2024-05-29 22:25 ` srinivas pandruvada
2024-05-30 7:41 ` Zhang, Lixu
2024-05-31 8:51 ` Zhang, Lixu
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=dd2a2483-0ad4-4563-8cc2-885a47a96e71@app.fastmail.com \
--to=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=bentiss@kernel.org \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).