Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kendall Willis <k-willis@ti.com>
To: Nishanth Menon <nm@ti.com>
Cc: "Kumar, Udit" <u-kumar1@ti.com>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Tero Kristo <kristo@kernel.org>, Rob Herring <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>, <s-kochidanadu@ti.com>,
	<a-kaur@ti.com>, <s-tripathi1@ti.com>, <vishalm@ti.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 3/3] arm64: dts: ti: k3-am62p: use ti,am62-m_can compatible for m_can devices
Date: Fri, 11 Sep 2026 09:32:05 -0500	[thread overview]
Message-ID: <20260911143205.pecdvyzsiokdvpy2@uda0506412> (raw)
In-Reply-To: <20260911035535.eexmc5g3rdwyahl7@speed>

Hi Nishanth,
On 22:55-20260910, Nishanth Menon wrote:
> On 09:59-20260904, Kendall Willis wrote:
> [...]
> 
> > Yes, that is essentially what the following patch is doing. But for CAN
> > devices, there is a chance that not all pinctrl_state_wakeup have
> > out-of-band wakeup functionality which is why the compatible is needed.
> > https://lore.kernel.org/all/20260902-temp-v4-2-3896f7d16ce8@ti.com/
> >
> 
> After looking at this driver side thread, Lets look at the DT series
> once the driver series has hit master. I am going to skip this series
> for this window.
> 
> Additionally, for future reference, will be good to state explicitly
> this kind of driver series dependency in patch diffstat or
> cover-letter[1] for example ti,am62-m_can does'nt exist on
> next-20260909 or master.
> 
> [1] https://lore.kernel.org/linux-arm-kernel/20260902-smth-v2-0-b3678ca44c7b@ti.com/

The dependency is listed in the cover letter, but is there a certain
way I should list it in the future so it is more clear?

Best,
Kendall


  reply	other threads:[~2026-09-11 14:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-02 21:04 [PATCH v2 0/3] arm64: dts: ti: use ti,am62-m_can compatible for m_can devices Kendall Willis
2026-09-02 21:04 ` [PATCH v2 1/3] arm64: dts: ti: k3-am62: " Kendall Willis
2026-09-02 21:04 ` [PATCH v2 2/3] arm64: dts: ti: k3-am62a: " Kendall Willis
2026-09-02 21:04 ` [PATCH v2 3/3] arm64: dts: ti: k3-am62p: " Kendall Willis
2026-09-04 14:09   ` Kumar, Udit
2026-09-04 14:59     ` Kendall Willis
2026-09-11  3:55       ` Nishanth Menon
2026-09-11 14:32         ` Kendall Willis [this message]
2026-09-11 19:19           ` Nishanth Menon
2026-09-11 19:46             ` Kendall Willis

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=20260911143205.pecdvyzsiokdvpy2@uda0506412 \
    --to=k-willis@ti.com \
    --cc=a-kaur@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kristo@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=robh@kernel.org \
    --cc=s-kochidanadu@ti.com \
    --cc=s-tripathi1@ti.com \
    --cc=u-kumar1@ti.com \
    --cc=vigneshr@ti.com \
    --cc=vishalm@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