From: "Michael Walle" <mwalle@kernel.org>
To: "Jakub Kicinski" <kuba@kernel.org>
Cc: "Vinod Koul" <vkoul@kernel.org>,
"Kishon Vijay Abraham I" <kishon@kernel.org>,
"Siddharth Vadapalli" <s-vadapalli@ti.com>,
"Matthias Schiffer" <matthias.schiffer@ew.tq-group.com>,
"Andrew Lunn" <andrew@lunn.ch>, <linux-phy@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<nm@ti.com>, <vigneshr@ti.com>
Subject: Re: [PATCH v3] phy: ti: gmii-sel: Always write the RGMII ID setting
Date: Fri, 22 Aug 2025 08:45:33 +0200 [thread overview]
Message-ID: <DC8R5IJ2Q88K.YKUE9X9FZRNK@kernel.org> (raw)
In-Reply-To: <20250821181850.6af0ff7f@kernel.org>
[-- Attachment #1.1: Type: text/plain, Size: 369 bytes --]
Hi,
On Fri Aug 22, 2025 at 3:18 AM CEST, Jakub Kicinski wrote:
> On Tue, 19 Aug 2025 08:56:22 +0200 Michael Walle wrote:
> > v3:
> > - simplify the logic. Thanks Matthias.
> > - reworded the commit message
>
> This was set to Not Applicable in our patchwork, IDK why.
> Could you resend?
Won't this patch be picked up by the linux-phy tree?
-michael
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 297 bytes --]
[-- Attachment #2: Type: text/plain, Size: 112 bytes --]
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
WARNING: multiple messages have this Message-ID (diff)
From: "Michael Walle" <mwalle@kernel.org>
To: "Jakub Kicinski" <kuba@kernel.org>
Cc: "Vinod Koul" <vkoul@kernel.org>,
"Kishon Vijay Abraham I" <kishon@kernel.org>,
"Siddharth Vadapalli" <s-vadapalli@ti.com>,
"Matthias Schiffer" <matthias.schiffer@ew.tq-group.com>,
"Andrew Lunn" <andrew@lunn.ch>, <linux-phy@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<nm@ti.com>, <vigneshr@ti.com>
Subject: Re: [PATCH v3] phy: ti: gmii-sel: Always write the RGMII ID setting
Date: Fri, 22 Aug 2025 08:45:33 +0200 [thread overview]
Message-ID: <DC8R5IJ2Q88K.YKUE9X9FZRNK@kernel.org> (raw)
In-Reply-To: <20250821181850.6af0ff7f@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 369 bytes --]
Hi,
On Fri Aug 22, 2025 at 3:18 AM CEST, Jakub Kicinski wrote:
> On Tue, 19 Aug 2025 08:56:22 +0200 Michael Walle wrote:
> > v3:
> > - simplify the logic. Thanks Matthias.
> > - reworded the commit message
>
> This was set to Not Applicable in our patchwork, IDK why.
> Could you resend?
Won't this patch be picked up by the linux-phy tree?
-michael
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 297 bytes --]
next prev parent reply other threads:[~2025-08-22 11:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 6:56 [PATCH v3] phy: ti: gmii-sel: Always write the RGMII ID setting Michael Walle
2025-08-19 6:56 ` Michael Walle
2025-08-19 9:45 ` Maxime Chevallier
2025-08-19 9:45 ` Maxime Chevallier
2025-08-22 1:18 ` Jakub Kicinski
2025-08-22 1:18 ` Jakub Kicinski
2025-08-22 6:45 ` Michael Walle [this message]
2025-08-22 6:45 ` Michael Walle
2025-08-22 14:01 ` Jakub Kicinski
2025-08-22 14:01 ` Jakub Kicinski
2025-09-01 17:03 ` Vinod Koul
2025-09-01 17:03 ` Vinod Koul
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=DC8R5IJ2Q88K.YKUE9X9FZRNK@kernel.org \
--to=mwalle@kernel.org \
--cc=andrew@lunn.ch \
--cc=kishon@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=matthias.schiffer@ew.tq-group.com \
--cc=netdev@vger.kernel.org \
--cc=nm@ti.com \
--cc=s-vadapalli@ti.com \
--cc=vigneshr@ti.com \
--cc=vkoul@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.