All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL]: Generic phy subsystem updates for v6.5-rc1
Date: Thu, 6 Jul 2023 01:14:58 +0530	[thread overview]
Message-ID: <ZKXIOnniqbMEcj4z@matsya> (raw)
In-Reply-To: <CAHk-=whPwD-7x=g9zR2xZ0=4EopwoJxaY=qX=T71vwWEcmaGWg@mail.gmail.com>

On 05-07-23, 11:16, Linus Torvalds wrote:
> On Wed, 5 Jul 2023 at 01:05, Vinod Koul <vkoul@kernel.org> wrote:
> >
> > Hello Linus,
> >
> >  - New support:
> >    - TI J784S4  gmii phy and SGMII support
> >    - Rockchip RK3588 naneng combo phy
> >    - Mediatek mt8195 hdmi phy
> >    - Qualcomm UFS PHY for sa8775p, SM7150, PCI phy for SDX65
> >    - Drop Thunder Bay eMMC PHY support
> >
> >  - Updates
> >    - Further cleanup for Qualcomm phys and support for PCIe RC
> >    - Xilinx zynqmp SGMII support
> >    - Cadence Sierra PCIe + SGMII PHY multilink configuration
> >    - Phy subsystem platform remove callback
> 
> Pretty much none of the explanations seem to be true. The Thunder Bay
> changes happened the last merge window.  The alleged 8195 changes do
> not seem to exist. The RK3588 changers are nowhere to be found.
> 
> And the sparx5 changes - that seem to be a noticeable part of this -
> aren't mentioned.

Sorry somehow I seemed to have reused old data while generating the tag
and email, I messed up!

> 
> I pulled, then unpulled.

Rightly so, I will send updated request, based on correct summary!

Apologies

-- 
~Vinod

  reply	other threads:[~2023-07-05 19:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-05  8:05 [GIT PULL]: Generic phy subsystem updates for v6.5-rc1 Vinod Koul
2023-07-05 18:16 ` Linus Torvalds
2023-07-05 19:44   ` Vinod Koul [this message]
2023-07-06  4:52 ` pr-tracker-bot

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=ZKXIOnniqbMEcj4z@matsya \
    --to=vkoul@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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.