From: <conor.dooley@microchip.com>
To: <mpm@selenic.com>, <herbert@gondor.apana.org.au>
Cc: <lewis.hanly@microchip.com>, <linux-kernel@vger.kernel.org>,
<linux-crypto@vger.kernel.org>, <linux-riscv@lists.infradead.org>,
"Conor Dooley" <conor.dooley@microchip.com>
Subject: [PATCH 2/2] MAINTAINERS: update PolarFire SoC support
Date: Mon, 7 Mar 2022 15:40:24 +0000 [thread overview]
Message-ID: <20220307154023.813158-3-conor.dooley@microchip.com> (raw)
In-Reply-To: <20220307154023.813158-1-conor.dooley@microchip.com>
From: Conor Dooley <conor.dooley@microchip.com>
Add mpfs-rng to the list of files included in PolarFire SoC support.
Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 573e5ee54162..dfbd076bddb6 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -16589,6 +16589,7 @@ RISC-V/MICROCHIP POLARFIRE SOC SUPPORT
M: Lewis Hanly <lewis.hanly@microchip.com>
L: linux-riscv@lists.infradead.org
S: Supported
+F: drivers/char/hw_random/mpfs-rng.c
F: drivers/mailbox/mailbox-mpfs.c
F: drivers/soc/microchip/
F: include/soc/microchip/mpfs.h
--
2.35.1
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2022-03-07 15:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 15:40 [PATCH 0/2] Add support for hwrng on PolarFire SoC conor.dooley
2022-03-07 15:40 ` [PATCH 1/2] hwrng: mpfs - add polarfire soc hwrng support conor.dooley
2022-03-08 7:55 ` Dominik Brodowski
2022-03-09 8:09 ` Conor.Dooley
2022-03-07 15:40 ` conor.dooley [this message]
2022-03-18 12:33 ` [PATCH 0/2] Add support for hwrng on PolarFire SoC 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=20220307154023.813158-3-conor.dooley@microchip.com \
--to=conor.dooley@microchip.com \
--cc=herbert@gondor.apana.org.au \
--cc=lewis.hanly@microchip.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mpm@selenic.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