public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH v1 0/2] bus: Remove Baikal SoC pieces
Date: Thu, 12 Mar 2026 11:23:11 +0200	[thread overview]
Message-ID: <abKF_1WR5_nc2xpL@ashevche-desk.local> (raw)
In-Reply-To: <20260311224356.GA1078900-robh@kernel.org>

On Wed, Mar 11, 2026 at 05:43:56PM -0500, Rob Herring wrote:
> On Fri, Feb 27, 2026 at 08:26:24AM +0100, Andy Shevchenko wrote:
> > Baikal SoC and platform support won't be finalised, remove stale pieces.
> > 
> > Andy Shevchenko (2):
> >   bus: Remove not-going-to-be-supported code for Baikal SoC
> >   dt-bindings: bus: Remove unused bindings
> 
> As there doesn't seem to be a maintainer for drivers/bus/, I just took 
> both patches.

Merci!

-- 
With Best Regards,
Andy Shevchenko



      reply	other threads:[~2026-03-12  9:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-27  7:26 [PATCH v1 0/2] bus: Remove Baikal SoC pieces Andy Shevchenko
2026-02-27  7:26 ` [PATCH v1 1/2] bus: Remove not-going-to-be-supported code for Baikal SoC Andy Shevchenko
2026-02-27  7:37   ` Randy Dunlap
2026-02-27  7:26 ` [PATCH v1 2/2] dt-bindings: bus: Remove unused bindings Andy Shevchenko
2026-02-27  7:37   ` Randy Dunlap
2026-03-11 22:43 ` [PATCH v1 0/2] bus: Remove Baikal SoC pieces Rob Herring
2026-03-12  9:23   ` Andy Shevchenko [this message]

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=abKF_1WR5_nc2xpL@ashevche-desk.local \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=rdunlap@infradead.org \
    --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