All of lore.kernel.org
 help / color / mirror / Atom feed
From: Damien Le Moal <dlemoal@kernel.org>
To: Conor Dooley <conor@kernel.org>, linux-riscv@lists.infradead.org
Cc: arnd@arndb.de, linux-kernel@vger.kernel.org,
	Paul Walmsley <pjw@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Alexandre Ghiti <alex@ghiti.fr>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: RISCV: canaan: Deprecated (oficially) the K210
Date: Fri, 9 Oct 2026 11:32:08 +0200	[thread overview]
Message-ID: <8d0fd503-4f4f-4cd1-9ae8-08ecd478b8cb@kernel.org> (raw)
In-Reply-To: <20261009-ee797bb64a30cf907f583aca@squawk>

On 2026/10/09 11:29, Conor Dooley wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
> 
> Two years ago, at LPC, the only known user of the k210, Damien, gave his
> okay to delete the platform from the kernel but this never actually took
> place. Deprecate the platform now, marking it as broken so that users
> will have to explicitly re-enable it on updating their kernels.
> 
> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>

Sad... But yeah, this platform never was really super useful in itself, beside
the code cleanups it generated.

Reviewed-by: Damien Le Moal <dlemoal@kernel.org>

-- 
Damien Le Moal
Western Digital Research

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2026-10-09  9:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-09  9:29 RISCV: canaan: Deprecated (oficially) the K210 Conor Dooley
2026-10-09  9:32 ` Damien Le Moal [this message]
2026-10-11 12:05   ` Geert Uytterhoeven

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=8d0fd503-4f4f-4cd1-9ae8-08ecd478b8cb@kernel.org \
    --to=dlemoal@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=arnd@arndb.de \
    --cc=conor@kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=pjw@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 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.