From: Kevin Hilman <khilman@baylibre.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
rogerq@kernel.org, tony@atomide.com, linux@treblig.org
Cc: linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] memory: omap-gpmc: deadcode a pair of functions
Date: Fri, 13 Dec 2024 09:14:07 -0800 [thread overview]
Message-ID: <7hikrncxpc.fsf@baylibre.com> (raw)
In-Reply-To: <76a403e0-f801-4d68-830c-370e0291efe1@kernel.org>
Krzysztof Kozlowski <krzk@kernel.org> writes:
> On 13/12/2024 17:45, Kevin Hilman wrote:
>>
>> On Wed, 11 Dec 2024 21:42:27 +0000, linux@treblig.org wrote:
>>> gpmc_get_client_irq() last use was removed by
>>> commit ac28e47ccc3f ("ARM: OMAP2+: Remove legacy gpmc-nand.c")
>>>
>>> gpmc_ticks_to_ns() last use was removed by
>>> commit 2514830b8b8c ("ARM: OMAP2+: Remove gpmc-onenand")
>>>
>>> Remove them.
>>>
>>> [...]
>>
>> Applied, thanks!
>>
>> [1/1] memory: omap-gpmc: deadcode a pair of functions
>> commit: 56d96fc5539003a95b8ab631a4ebb5d1b0a24885
>
> This should not go via soc tree, it's memory.
>
Indeed, thanks for catching. That's what I get for trying to
review/apply patches first thing in the moring.
I dropped it from my tree, sorry for the noise.
What should've said was simply
Acked-by: Kevin Hilman <khilman@baylibre.com>
Kevin
next prev parent reply other threads:[~2024-12-13 17:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 21:42 [PATCH v2] memory: omap-gpmc: deadcode a pair of functions linux
2024-12-12 12:04 ` Roger Quadros
2024-12-13 16:45 ` Kevin Hilman
2024-12-13 16:47 ` Krzysztof Kozlowski
2024-12-13 17:14 ` Kevin Hilman [this message]
2024-12-14 10:50 ` Krzysztof Kozlowski
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=7hikrncxpc.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@treblig.org \
--cc=rogerq@kernel.org \
--cc=tony@atomide.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