From: Nishanth Menon <nm@ti.com>
To: <vigneshr@ti.com>, <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <francesco@dolcini.it>,
Udit Kumar <u-kumar1@ti.com>
Cc: Nishanth Menon <nm@ti.com>, <kristo@kernel.org>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] Fix UART pin type and macro type
Date: Fri, 26 Apr 2024 17:39:40 -0500 [thread overview]
Message-ID: <171417117218.3482975.10699433624709237750.b4-ty@ti.com> (raw)
In-Reply-To: <20240415095605.3547933-1-u-kumar1@ti.com>
Hi Udit Kumar,
On Mon, 15 Apr 2024 15:26:03 +0530, Udit Kumar wrote:
> This series fixes UART pin mux for J784s4-evm and am69.
> Along with replacing pin mux macro of J784S4 SOC instead of J721S2.
>
> Test logs
> https://gist.github.com/uditkumarti/a28ec171732e32c16b2666c27093c115
>
> For fixes, these errors should be caught during review but missed due to
> cross reference is taken from tool's output.
> Note to self, don't always rely on tool's output while reviewing the patch.
>
> [...]
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/2] arm64: dts: ti: k3-j784s4-evm: Fix UART pin type and macro type
commit: d79fc91456338f42e9066cff91e3b4ea174986d4
[2/2] arm64: dts: ti: k3-am69-sk: Fix UART pin type and macro type
commit: e1818f04eff632bad803f85d24dbfbfa3ddb5218
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
prev parent reply other threads:[~2024-04-26 22:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 9:56 [PATCH v2 0/2] Fix UART pin type and macro type Udit Kumar
2024-04-15 9:56 ` [PATCH v2 1/2] arm64: dts: ti: k3-j784s4-evm: " Udit Kumar
2024-04-15 11:02 ` Francesco Dolcini
2024-04-15 9:56 ` [PATCH v2 2/2] arm64: dts: ti: k3-am69-sk: " Udit Kumar
2024-04-15 11:03 ` Francesco Dolcini
2024-04-26 22:39 ` Nishanth Menon [this message]
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=171417117218.3482975.10699433624709237750.b4-ty@ti.com \
--to=nm@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=francesco@dolcini.it \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=u-kumar1@ti.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).