From: Judith Mendez <jm@ti.com>
To: Nishanth Menon <nm@ti.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Dmitry Baryshkov <lumag@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>
Subject: Re: [PATCH] arm64: defconfig: Enable hwspinlock and eQEP for K3
Date: Tue, 22 Apr 2025 09:23:26 -0500 [thread overview]
Message-ID: <86938add-1ccc-4be3-af3f-cff911c96d42@ti.com> (raw)
In-Reply-To: <20250422142207.2tu7gmhnjercmoa2@basil>
Hi Nishanth,
On 4/22/25 9:22 AM, Nishanth Menon wrote:
> On 09:15-20250422, Judith Mendez wrote:
>> Hi Arnd,
>>
>> On 4/22/25 1:37 AM, Arnd Bergmann wrote:
>>> On Mon, Apr 21, 2025, at 22:10, Judith Mendez wrote:
>>>> Enable CONFIG_HWSPINLOCK_OMAP to allow usage of these devices
>>>> across K3 SoC's. Also enable CONFIG_TI_EQEP which is enabled by
>>>> default on am64x SK board.
>>>>
>>>> Signed-off-by: Judith Mendez <jm@ti.com>
>>>
>>> Acked-by: Arnd Bergmann <arnd@arndb.de>
>>>
>>> The patch seems fine to me, but you should address it at the
>>> TI K3 maintainers, so they know they should apply it and forward
>>> it to the SoC tree. You have Nishanth and Vignesh in Cc already,
>>> so I assume they will pick it up from here, just put them in
>>> 'To' instead next time and move Catalin and Will to 'Cc' or
>>> leave them off entirely.
>>>
>>
>> Will re-spin and fix the to and cc lists, thanks for reviewing!
>
> There is no need to respin, it is already in my queue. Will pick it up
> as part of usual process. The above information that Arnd provided is
> for future reference.
>
Sounds good, thanks for the help.
~ Judith
next prev parent reply other threads:[~2025-04-22 14:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 20:10 [PATCH] arm64: defconfig: Enable hwspinlock and eQEP for K3 Judith Mendez
2025-04-22 6:37 ` Arnd Bergmann
2025-04-22 14:15 ` Judith Mendez
2025-04-22 14:22 ` Nishanth Menon
2025-04-22 14:23 ` Judith Mendez [this message]
2025-04-25 21:13 ` Nishanth Menon
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=86938add-1ccc-4be3-af3f-cff911c96d42@ti.com \
--to=jm@ti.com \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@oss.qualcomm.com \
--cc=catalin.marinas@arm.com \
--cc=geert+renesas@glider.be \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=nm@ti.com \
--cc=vigneshr@ti.com \
--cc=will@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox