From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH v2 1/1] mtd: physmap: physmap-bt1-rom: Remove not-going-to-be-supported code for Baikal SoC
Date: Wed, 11 Mar 2026 10:09:35 +0100 [thread overview]
Message-ID: <875x72n35c.fsf@bootlin.com> (raw)
In-Reply-To: <abAEN7_1aQjSxYhc@ashevche-desk.local> (Andy Shevchenko's message of "Tue, 10 Mar 2026 13:44:55 +0200")
On 10/03/2026 at 13:44:55 +02, Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> On Wed, Feb 25, 2026 at 05:23:34PM +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.
>
> Can this be moved forward?
Yes, I reviewed it and I plan to apply it. I will do a round of
applied/thanks soon.
Cheers,
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH v2 1/1] mtd: physmap: physmap-bt1-rom: Remove not-going-to-be-supported code for Baikal SoC
Date: Wed, 11 Mar 2026 10:09:35 +0100 [thread overview]
Message-ID: <875x72n35c.fsf@bootlin.com> (raw)
In-Reply-To: <abAEN7_1aQjSxYhc@ashevche-desk.local> (Andy Shevchenko's message of "Tue, 10 Mar 2026 13:44:55 +0200")
On 10/03/2026 at 13:44:55 +02, Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> On Wed, Feb 25, 2026 at 05:23:34PM +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.
>
> Can this be moved forward?
Yes, I reviewed it and I plan to apply it. I will do a round of
applied/thanks soon.
Cheers,
Miquèl
next prev parent reply other threads:[~2026-03-11 9:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 16:23 [PATCH v2 1/1] mtd: physmap: physmap-bt1-rom: Remove not-going-to-be-supported code for Baikal SoC Andy Shevchenko
2026-02-25 16:23 ` Andy Shevchenko
2026-03-10 11:44 ` Andy Shevchenko
2026-03-10 11:44 ` Andy Shevchenko
2026-03-11 9:09 ` Miquel Raynal [this message]
2026-03-11 9:09 ` Miquel Raynal
2026-03-11 12:08 ` Andy Shevchenko
2026-03-11 12:08 ` Andy Shevchenko
2026-03-11 15:25 ` Miquel Raynal
2026-03-11 15:25 ` Miquel Raynal
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=875x72n35c.fsf@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=rdunlap@infradead.org \
--cc=richard@nod.at \
--cc=vigneshr@ti.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.