All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Sebastian Huber <sebastian.huber@embedded-brains.de>
Cc: Alistair Francis <alistair23@gmail.com>,
	 Palmer Dabbelt <palmer@dabbelt.com>,
	 liwei1518@gmail.com,
	 daniel barboza <daniel.barboza@oss.qualcomm.com>,
	 zhiwei liu <zhiwei_liu@linux.alibaba.com>,
	 chao liu zevorn <chao.liu.zevorn@gmail.com>,
	 qemu-riscv <qemu-riscv@nongnu.org>,
	qemu-devel <qemu-devel@nongnu.org>,
	 Conor Dooley <conor@kernel.org>,
	alistair francis <alistair.francis@wdc.com>
Subject: Re: [PATCH] MAINTAINERS: Mark Microchip PolarFire SoC as Odd Fixes
Date: Wed, 13 May 2026 07:56:42 +0200	[thread overview]
Message-ID: <87mry3vomd.fsf@pond.sub.org> (raw)
In-Reply-To: <1514447636.13520.1778641704122.JavaMail.zimbra@embedded-brains.de> (Sebastian Huber's message of "Wed, 13 May 2026 05:08:24 +0200 (CEST)")

Sebastian Huber <sebastian.huber@embedded-brains.de> writes:

> ----- Am 13. Mai 2026 um 4:38 schrieb Alistair Francis alistair23@gmail.com:
>
>> From: Alistair Francis <alistair.francis@wdc.com>
>> 
>> Mark the "Microchip PolarFire SoC Icicle Kit" as Odd Fixes and enlist
>> Conor and Sebastian as people to help deal with the fixes.
>> 
>> Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
>
> Thanks, this is fine.

Can you make it official?  Acked-by: ...

Thanks!



  reply	other threads:[~2026-05-13  5:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-13  2:38 [PATCH] MAINTAINERS: Mark Microchip PolarFire SoC as Odd Fixes alistair23
2026-05-13  3:08 ` Sebastian Huber
2026-05-13  5:56   ` Markus Armbruster [this message]
2026-05-13  6:07     ` Sebastian Huber
2026-05-13  6:10 ` Philippe Mathieu-Daudé
2026-05-13 21:26   ` Conor Dooley
2026-05-13 21:31     ` Guenter Roeck
2026-05-13 23:54     ` Alistair Francis
2026-05-14  9:59       ` Conor Dooley
2026-05-13 19:18 ` Conor Dooley

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=87mry3vomd.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=alistair.francis@wdc.com \
    --cc=alistair23@gmail.com \
    --cc=chao.liu.zevorn@gmail.com \
    --cc=conor@kernel.org \
    --cc=daniel.barboza@oss.qualcomm.com \
    --cc=liwei1518@gmail.com \
    --cc=palmer@dabbelt.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-riscv@nongnu.org \
    --cc=sebastian.huber@embedded-brains.de \
    --cc=zhiwei_liu@linux.alibaba.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.