From: Sasha Levin <sashal@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org,
"Clément Le Goffic" <clement.legoffic@foss.st.com>,
"Alain Volmat" <alain.volmat@foss.st.com>,
"Andi Shyti" <andi.shyti@kernel.org>
Subject: Re: [PATCH 6.6.y 5/6] i2c: stm32: fix the device used for the DMA map
Date: Wed, 30 Jul 2025 09:50:04 -0400 [thread overview]
Message-ID: <aIojDG3rheLDMVzC@lappy> (raw)
In-Reply-To: <2025073007-swapping-upcountry-fd02@gregkh>
On Wed, Jul 30, 2025 at 11:03:34AM +0200, Greg KH wrote:
>On Tue, Jul 22, 2025 at 08:19:41PM -0400, Sasha Levin wrote:
>> From: Clément Le Goffic <clement.legoffic@foss.st.com>
>>
>> [ Upstream commit c870cbbd71fccda71d575f0acd4a8d2b7cd88861 ]
>>
>> If the DMA mapping failed, it produced an error log with the wrong
>> device name:
>> "stm32-dma3 40400000.dma-controller: rejecting DMA map of vmalloc memory"
>> Fix this issue by replacing the dev with the I2C dev.
>>
>> Fixes: bb8822cbbc53 ("i2c: i2c-stm32: Add generic DMA API")
>> Signed-off-by: Clément Le Goffic <clement.legoffic@foss.st.com>
>> Cc: <stable@vger.kernel.org> # v4.18+
>> Acked-by: Alain Volmat <alain.volmat@foss.st.com>
>> Signed-off-by: Andi Shyti <andi.shyti@kernel.org>
>> Link: https://lore.kernel.org/r/20250704-i2c-upstream-v4-1-84a095a2c728@foss.st.com
>> Signed-off-by: Sasha Levin <sashal@kernel.org>
>> ---
>> drivers/i2c/busses/i2c-stm32.c | 8 +++-----
>> drivers/i2c/busses/i2c-stm32f7.c | 4 ++--
>> 2 files changed, 5 insertions(+), 7 deletions(-)
>
>This is already in 6.6.100, so are you sure you want it again? :)
>
>Care to redo this series?
Looks like we raced on that one. I'l send out a v2.
--
Thanks,
Sasha
next prev parent reply other threads:[~2025-07-30 13:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 9:24 FAILED: patch "[PATCH] i2c: stm32f7: unmap DMA mapped buffer" failed to apply to 6.6-stable tree gregkh
2025-07-23 0:19 ` [PATCH 6.6.y 1/6] i2c: stm32f7: Use devm_clk_get_enabled() Sasha Levin
2025-07-23 0:19 ` [PATCH 6.6.y 2/6] i2c: stm32f7: use dev_err_probe upon calls of devm_request_irq Sasha Levin
2025-07-23 0:19 ` [PATCH 6.6.y 3/6] i2c: stm32f7: perform most of irq job in threaded handler Sasha Levin
2025-07-23 0:19 ` [PATCH 6.6.y 4/6] i2c: stm32f7: simplify status messages in case of errors Sasha Levin
2025-07-23 0:19 ` [PATCH 6.6.y 5/6] i2c: stm32: fix the device used for the DMA map Sasha Levin
2025-07-30 9:03 ` Greg KH
2025-07-30 13:50 ` Sasha Levin [this message]
2025-07-23 0:19 ` [PATCH 6.6.y 6/6] i2c: stm32f7: unmap DMA mapped buffer Sasha Levin
2025-07-30 13:59 ` [PATCH 6.6.y v2 1/5] i2c: stm32f7: Use devm_clk_get_enabled() Sasha Levin
2025-07-30 13:59 ` [PATCH 6.6.y v2 2/5] i2c: stm32f7: use dev_err_probe upon calls of devm_request_irq Sasha Levin
2025-07-30 14:00 ` [PATCH 6.6.y v2 3/5] i2c: stm32f7: perform most of irq job in threaded handler Sasha Levin
2025-07-30 14:00 ` [PATCH 6.6.y v2 4/5] i2c: stm32f7: simplify status messages in case of errors Sasha Levin
2025-07-30 14:00 ` [PATCH 6.6.y v2 5/5] i2c: stm32f7: unmap DMA mapped buffer Sasha Levin
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=aIojDG3rheLDMVzC@lappy \
--to=sashal@kernel.org \
--cc=alain.volmat@foss.st.com \
--cc=andi.shyti@kernel.org \
--cc=clement.legoffic@foss.st.com \
--cc=gregkh@linuxfoundation.org \
--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.