public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor.dooley@microchip.com>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
	Albert Ou <aou@eecs.berkeley.edu>, <linux-kernel@vger.kernel.org>,
	<linux-riscv@lists.infradead.org>, <daire.mcnamara@microchip.com>,
	<lewis.hanly@microchip.com>, <cyril.jean@microchip.com>,
	Conor Dooley <conor.dooley@microchip.com>
Subject: [PATCH v4 0/1] polarfire soc kconfig/maintainers updates
Date: Thu, 5 May 2022 11:55:25 +0100	[thread overview]
Message-ID: <20220505105525.3881259-1-conor.dooley@microchip.com> (raw)

Hey Palmer,

As I said yesterday on IRC, for v4 of this patchset I have removed
the kconfig changes, pending deciding on a better/consistent way
of using the SOC_FOO symbols in kconfig.socs.
The only remaining patch in this set is now the MAINTAINERS update
which was patch 4/4 in v3.

Thanks,
Conor.

Conor Dooley (1):
  MAINTAINERS: add polarfire rng, pci and clock drivers

 MAINTAINERS | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

-- 
2.35.2


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

             reply	other threads:[~2022-05-05 10:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-05 10:55 Conor Dooley [this message]
2022-05-05 10:55 ` [PATCH v4 1/1] MAINTAINERS: add polarfire rng, pci and clock drivers Conor Dooley
2022-05-23 11:42   ` Conor.Dooley
2022-05-23 19:52     ` Palmer Dabbelt
2022-05-23 20:00       ` Conor.Dooley
2022-06-02  1:55         ` Palmer Dabbelt
2022-06-02  4:39           ` Conor.Dooley
2022-06-02 16:31             ` Bjorn Helgaas
2022-06-02 22:05               ` Palmer Dabbelt
2022-06-02 16:03           ` Bjorn Helgaas
2022-06-09 22:43           ` Stephen Boyd
2022-06-09 22:53             ` 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=20220505105525.3881259-1-conor.dooley@microchip.com \
    --to=conor.dooley@microchip.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=cyril.jean@microchip.com \
    --cc=daire.mcnamara@microchip.com \
    --cc=lewis.hanly@microchip.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox