From: Greg KH <gregkh@linuxfoundation.org>
To: PRC Automation <prc@list.ti.com>
Cc: Siddharth Vadapalli <s-vadapalli@ti.com>,
praneeth@ti.com, u-kumar1@ti.com, vigneshr@ti.com,
stable@vger.kernel.org
Subject: Re: [tiL6.18 PATCH] FROMLIST: arm64: dts: ti: k3-am62d2-evm: Fix missing RX delay for DP83867 PHY
Date: Sat, 24 Jan 2026 09:23:40 +0100 [thread overview]
Message-ID: <2026012406-saga-tactical-fd5e@gregkh> (raw)
In-Reply-To: <20260124080029.2810485-1-prc@list.ti.com>
On Sat, Jan 24, 2026 at 02:00:29AM -0600, PRC Automation wrote:
> ti-kernel / 6.18 / 20260124070651.2152967-1-s-vadapalli
>
> PRC Results: FAIL
>
> =========================================================
> apply-patch: PASS
> =========================================================
> Summary:
> - Patch Series: [tiL6.18 PATCH] FROMLIST: arm64: dts: ti: k3-am62d2-evm: Fix missing RX delay for DP83867 PHY
> - Submitter: From: Siddharth Vadapalli <s-vadapalli@ti.com>
> - Date: Date: Sat, 24 Jan 2026 12:36:46 +0530
> - Num Patches: 1
> - Mailing List (public inbox) Commit SHA: 17b1d51fe2ff3be3a867d71baf22dbb3153135b6
>
> Applied to:
> - Repository: lcpd-prc-ti-linux-kernel
> - Base Branch: ti-linux-6.18.y-cicd
> - Commit Author: Parvathi Pudi <parvathi@couthit.com>
> - Commit Subject: UPSTREAM: ARM: multi_v7_defconfig: Enable TI PRU Ethernet driver
> - Commit SHA: 3e1b5fb10cace2688eecd366e85af7c1f5a69fac
>
> Patches
> ----------------------------------------
> All patches applied
Was this email ment to be sent to stable@vger.kernel.org? If not,
please fix up your scripts. If so, what are we supposed to do with
this?
thanks,
greg k-h
next prev parent reply other threads:[~2026-01-24 8:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260124070651.2152967-1-s-vadapalli@ti.com>
2026-01-24 8:00 ` [tiL6.18 PATCH] FROMLIST: arm64: dts: ti: k3-am62d2-evm: Fix missing RX delay for DP83867 PHY PRC Automation
2026-01-24 8:23 ` Greg KH [this message]
2026-01-27 3:03 ` Bajjuri, Praneeth
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=2026012406-saga-tactical-fd5e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=praneeth@ti.com \
--cc=prc@list.ti.com \
--cc=s-vadapalli@ti.com \
--cc=stable@vger.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