From: Beleswar Prasad Padhi <b-padhi@ti.com>
To: Krzysztof Kozlowski <krzk@kernel.org>, <linux@armlinux.org.uk>,
<arnd@arndb.de>
Cc: <afd@ti.com>, <u-kumar1@ti.com>, <praneeth@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] arm: multi_v7_defconfig: Enable more OMAP related configs
Date: Mon, 9 Feb 2026 16:09:09 +0530 [thread overview]
Message-ID: <f1f27a4f-c8d1-409d-9915-ec7476950bcc@ti.com> (raw)
In-Reply-To: <c218f45f-d3cd-4a72-8af5-91ef59ff6936@kernel.org>
On 09/02/26 15:12, Krzysztof Kozlowski wrote:
> On 09/02/2026 10:39, Beleswar Prasad Padhi wrote:
>> Hi all,
>>
>> On 16/06/25 13:50, Beleswar Padhi wrote:
>>> From: Sinthu Raja <sinthu.raja@ti.com>
>>>
>>> This allows us to enable various peripherals in the TI OMAP family
>>> platforms like AM571X-IDK, AM572X-IDK, AM574X-IDK, AM57XX-BEAGLE-X15,
>>> AM57XX-EVM using the multi_v7_defconfig, instead of only with the
>>> OMAP specific defconfigs.
>>
>> [...]
>>
>>> Signed-off-by: Sinthu Raja <sinthu.raja@ti.com>
>>> Signed-off-by: Beleswar Padhi <b-padhi@ti.com>
>>> ---
>>> v2: Changelog:
>>> Krzysztof:
>>> 1. Updated commit message to call out which (and why) upstream boards
>>> need these configs to be enabled.
>>> 2. Used savedefconfig to correct the order of configs in the defconfig.
>>
>> A gentle ping on this patch. All of the drivers are enabled as
>> modules in this patch and the existing review comments
>> have been addressed.
>>
>> Please help in a review/merge.
>
> There are no full names next to the emails, so I cannot verify that you
> actually Cc-ed right people, but it just looks like you did not. If you
> do not Cc the intended maintainer, then the maintainer will not pick it
> up. Neither Arnd nor me are OMAP maintainers.
Thanks, you're right.. will resend the patch with OMAP
maintainers.
Thanks,
Beleswar
next prev parent reply other threads:[~2026-02-09 10:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 8:20 Beleswar Padhi
2026-02-09 9:39 ` Beleswar Prasad Padhi
2026-02-09 9:42 ` Krzysztof Kozlowski
2026-02-09 10:39 ` Beleswar Prasad Padhi [this message]
2025-08-19 10:11 Beleswar Padhi
2025-08-19 11:26 ` Krzysztof Kozlowski
2025-08-21 18:27 ` Kevin Hilman
2025-08-21 23:17 ` Judith Mendez
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=f1f27a4f-c8d1-409d-9915-ec7476950bcc@ti.com \
--to=b-padhi@ti.com \
--cc=afd@ti.com \
--cc=arnd@arndb.de \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=praneeth@ti.com \
--cc=u-kumar1@ti.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
all inboxes | Powered by JetHome®