From: Yemike Abhilash Chandra <y-abhilashchandra@ti.com>
To: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Cc: <linusw@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <nm@ti.com>, <vigneshr@ti.com>,
<kristo@kernel.org>, <brgl@kernel.org>,
<linux-gpio@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<afd@ti.com>, <u-kumar1@ti.com>
Subject: Re: [PATCH 2/3] pinctrl: ti: Add TDA54 pin controller driver
Date: Tue, 13 Oct 2026 11:39:26 +0530 [thread overview]
Message-ID: <82b4e933-f36e-4eb8-b087-85002b85c0b5@ti.com> (raw)
In-Reply-To: <aswXWWBwo22nQ4RR@monoceros>
Hi Uwe,
On 12/10/26 04:41, Uwe Kleine-König wrote:
> On Wed, Sep 30, 2026 at 02:50:19PM +0530, Yemike Abhilash Chandra wrote:
>> +#include <linux/mod_devicetable.h>
>
> Please don't add new users of this header. You can rely on
> <linux/platform_device.h> to provide of_device_id.
>
Thanks for the review. Sure, will drop that.
Thanks and regards,
Yemike Abhilash Chandra
> Best regards
> Uwe
next prev parent reply other threads:[~2026-10-13 6:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 9:20 [PATCH 0/3] Add pin controller support for TI TDA54 SoC Yemike Abhilash Chandra
2026-09-30 9:20 ` [PATCH 1/3] dt-bindings: pinctrl: Add TI TDA54 pin controller Yemike Abhilash Chandra
2026-10-01 21:10 ` Linus Walleij
2026-10-01 21:26 ` Conor Dooley
2026-09-30 9:20 ` [PATCH 2/3] pinctrl: ti: Add TDA54 pin controller driver Yemike Abhilash Chandra
2026-10-01 20:52 ` Linus Walleij
2026-10-13 6:00 ` Yemike Abhilash Chandra
2026-10-11 23:11 ` Uwe Kleine-König
2026-10-13 6:09 ` Yemike Abhilash Chandra [this message]
2026-09-30 9:20 ` [PATCH 3/3] arm64: dts: ti: Add TDA54 pinctrl header Yemike Abhilash Chandra
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=82b4e933-f36e-4eb8-b087-85002b85c0b5@ti.com \
--to=y-abhilashchandra@ti.com \
--cc=afd@ti.com \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=u-kumar1@ti.com \
--cc=u.kleine-koenig@baylibre.com \
--cc=vigneshr@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®