public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Rob Herring (Arm)" <robh@kernel.org>
Cc: linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
	"Manivannan Sadhasivam" <mani@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Philipp Zabel" <p.zabel@pengutronix.de>,
	"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>
Subject: Re: [PATCH v2 1/1] PCI: dwc: Remove not-going-to-be-supported code for Baikal SoC
Date: Mon, 2 Mar 2026 15:33:49 +0200	[thread overview]
Message-ID: <aaWRveAPxWpHosPs@ashevche-desk.local> (raw)
In-Reply-To: <177187310274.163191.14167430732235845058.robh@kernel.org>

On Mon, Feb 23, 2026 at 12:58:24PM -0600, Rob Herring (Arm) wrote:
> On Fri, 20 Feb 2026 15:21:12 +0100, Andy Shevchenko wrote:
> > As noticed in the discussion [1] the Baikal SoC and platforms
> > are not going to be finalized, hence remove stale code.

> Acked-by: Rob Herring (Arm) <robh@kernel.org>

Thanks, Rob!

Any chances to see this in PCI tree?

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2026-03-02 13:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-20 14:21 [PATCH v2 1/1] PCI: dwc: Remove not-going-to-be-supported code for Baikal SoC Andy Shevchenko
2026-02-23 18:58 ` Rob Herring (Arm)
2026-03-02 13:33   ` Andy Shevchenko [this message]
2026-03-02 13:51 ` Manivannan Sadhasivam
2026-03-02 13:57   ` Andy Shevchenko
2026-03-02 14:07     ` Manivannan Sadhasivam
2026-03-02 14:16       ` Andy Shevchenko
2026-03-02 14:12 ` Manivannan Sadhasivam

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=aaWRveAPxWpHosPs@ashevche-desk.local \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=bhelgaas@google.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=kwilczynski@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=mani@kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox