All of lore.kernel.org
 help / color / mirror / Atom feed
From: Li Chen <me@linux.beauty>
To: "Bjorn Helgaas" <helgaas@kernel.org>
Cc: "Tom Joseph" <tjoseph@cadence.com>,
	"Parshuram Thombare" <pthombar@cadence.com>,
	"Pawel Laszczak" <pawell@cadence.com>,
	"\"Przemysław Gaj\"" <pgaj@cadence.com>,
	"Nadeem Athani" <nadeem@cadence.com>,
	"Siddharth Vadapalli" <s-vadapalli@ti.com>,
	"Kishon Vijay Abraham I" <kishon@ti.com>,
	"\"Krzysztof Wilczyński\"" <kwilczynski@kernel.org>,
	"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
	linux-pci <linux-pci@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Is Cadence PCIe IP orphaned?
Date: Fri, 29 Dec 2023 04:46:11 -0500	[thread overview]
Message-ID: <18cb4f78be7.118217ede232604.6825928402358580565@linux.beauty> (raw)
In-Reply-To: <20231228134132.GA1486379@bhelgaas>

Hi Bjorn,

 ---- On Thu, 28 Dec 2023 08:41:32 -0500  Bjorn Helgaas  wrote --- 
 > Tom Joseph tjoseph@cadence.com> is listed as the maintainer of the
 > Cadence PCIe IP, but email to that address bounces and lore has no
 > correspondence from Tom in the past two years
 > (https://lore.kernel.org/all/?q=f%3Atjoseph).
 > 
 > Does anybody want to step up to maintain this?  Should we apply a
 > patch like the one below?

AFAIK, Cadence people are preparing to upstream their Gen5 controller and PHY drivers. They may update the maintainers when they do so.

Regards,
Li


  reply	other threads:[~2023-12-29  9:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-28 13:41 Is Cadence PCIe IP orphaned? Bjorn Helgaas
2023-12-29  9:46 ` Li Chen [this message]
2024-01-02 18:21   ` Bjorn Helgaas

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=18cb4f78be7.118217ede232604.6825928402358580565@linux.beauty \
    --to=me@linux.beauty \
    --cc=helgaas@kernel.org \
    --cc=kishon@ti.com \
    --cc=kwilczynski@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=nadeem@cadence.com \
    --cc=pawell@cadence.com \
    --cc=pgaj@cadence.com \
    --cc=pthombar@cadence.com \
    --cc=s-vadapalli@ti.com \
    --cc=tjoseph@cadence.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 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.