mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vignesh Raghavendra <vigneshr@ti.com>
To: Siddharth Vadapalli <s-vadapalli@ti.com>
Cc: <nm@ti.com>, <kristo@kernel.org>, <robh@kernel.org>,
	<krzk+dt@kernel.org>, <conor+dt@kernel.org>,
	<y-abhilashchandra@ti.com>, <u-kumar1@ti.com>,
	<stable@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>, <srk@ti.com>
Subject: Re: [PATCH] arm64: dts: ti: k3-j721e-sk: Fix pinmux for power regulator
Date: Wed, 19 Nov 2025 19:57:58 +0530	[thread overview]
Message-ID: <6d6a1eeb-503d-48be-81bb-df53942b321c@ti.com> (raw)
In-Reply-To: <371e6a49846f910e9a747d4185471806cc719138.camel@ti.com>



On 19/11/25 14:13, Siddharth Vadapalli wrote:
> On Wed, 2025-11-19 at 13:38 +0530, Vignesh Raghavendra wrote:
> 
> Hello Vignesh,
> 
>>
>> On 18/11/25 17:19, Siddharth Vadapalli wrote:
>>> Commit under Fixes added support for power regulators on the J721E SK
>>
>> ^^^ not the right way to quote a commit. Should follow commit SHA
> 
> I started following this format after I noticed that an earlier patch of
> mine at [0]
> was merged to the Networking Tree with the commit message updated to follow
> this format [1]. I acknowledge that the expected format might be different
> across subsystems, but I used this format since it seemed concise to me and
> I believe that it makes it easier for the reader.
> 

Ok,  seems common in netdev but not outside of that tree.

> However, if the format should be:
> commit SHA ("$subject")
> for the TI-K3-DTS Tree as a policy, I will fix the format and post the v2
> patch.
> 
> [0]: https://lore.kernel.org/r/20241220075618.228202-1-s-vadapalli@ti.com/
> [1]:
> https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=4a4d38ace1fb
> 
>> ("$subject") format. Moreover this paragraph can be simply be stated as
>> node is under wrong pmx region (wakeup) and instead should be moved to main
> 
> Please let me know if I should post a v2 for this or if you plan to correct
> it locally
> (in case the 'commit SHA ("$subject") format doesn't require a v2).

There really is no need to quote the offending commit as part of the
text as Fixes Tag makes it obvious. You would just have to describe that
node is in the wrong parent node and needs to be moved under main pmx
node with appropriate reference to TRM/Doc

> 
> Regards,
> Siddharth.

-- 
Regards
Vignesh
https://ti.com/opensource


  reply	other threads:[~2025-11-19 14:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-18 11:49 Siddharth Vadapalli
2025-11-19  6:04 ` Yemike Abhilash Chandra
2025-11-19  8:08 ` Vignesh Raghavendra
2025-11-19  8:43   ` Siddharth Vadapalli
2025-11-19 14:27     ` Vignesh Raghavendra [this message]
2025-11-19 15:30       ` Siddharth Vadapalli

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=6d6a1eeb-503d-48be-81bb-df53942b321c@ti.com \
    --to=vigneshr@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-vadapalli@ti.com \
    --cc=srk@ti.com \
    --cc=stable@vger.kernel.org \
    --cc=u-kumar1@ti.com \
    --cc=y-abhilashchandra@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®