Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Atish Patra <atishp@rivosinc.com>
To: linux-kernel@vger.kernel.org
Cc: Atish Patra <atishp@rivosinc.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Atish Patra <atishp@atishpatra.org>,
	Anup Patel <anup@brainfault.org>,
	Damien Le Moal <damien.lemoal@wdc.com>,
	devicetree@vger.kernel.org, Jisheng Zhang <jszhang@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
	linux-riscv@lists.infradead.org,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Rob Herring <robh+dt@kernel.org>
Subject: [v6 9/9] MAINTAINERS: Add entry for RISC-V PMU drivers
Date: Fri, 18 Feb 2022 16:47:00 -0800	[thread overview]
Message-ID: <20220219004700.1973682-10-atishp@rivosinc.com> (raw)
In-Reply-To: <20220219004700.1973682-1-atishp@rivosinc.com>

From: Atish Patra <atish.patra@wdc.com>

Add myself and Anup as maintainer for RISC-V PMU drivers.

Signed-off-by: Atish Patra <atish.patra@wdc.com>
Signed-off-by: Atish Patra <atishp@rivosinc.com>
---
 MAINTAINERS | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index fca970a46e77..101a07728d5f 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -16596,6 +16596,15 @@ S:	Maintained
 F:	drivers/mtd/nand/raw/r852.c
 F:	drivers/mtd/nand/raw/r852.h
 
+RISC-V PMU DRIVERS
+M:	Atish Patra <atishp@atishpatra.org>
+R:	Anup Patel <anup@brainfault.org>
+L:	linux-riscv@lists.infradead.org
+S:	Supported
+F:	drivers/perf/riscv_pmu.c
+F:	drivers/perf/riscv_pmu_legacy.c
+F:	drivers/perf/riscv_pmu_sbi.c
+
 RISC-V ARCHITECTURE
 M:	Paul Walmsley <paul.walmsley@sifive.com>
 M:	Palmer Dabbelt <palmer@dabbelt.com>
-- 
2.30.2


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

  parent reply	other threads:[~2022-02-19  0:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-19  0:46 [v6 0/9] Improve RISC-V Perf support using SBI PMU and sscofpmf extension Atish Patra
2022-02-19  0:46 ` [v6 1/9] RISC-V: Remove the current perf implementation Atish Patra
2022-02-19  0:46 ` [v6 2/9] RISC-V: Add CSR encodings for all HPMCOUNTERS Atish Patra
2022-02-19  0:46 ` [v6 3/9] RISC-V: Add a perf core library for pmu drivers Atish Patra
2022-02-19  0:46 ` [v6 4/9] RISC-V: Add a simple platform driver for RISC-V legacy perf Atish Patra
2022-02-19  0:46 ` [v6 5/9] RISC-V: Add RISC-V SBI PMU extension definitions Atish Patra
2022-02-19  0:46 ` [v6 6/9] RISC-V: Add perf platform driver based on SBI PMU extension Atish Patra
2022-02-19  0:46 ` [v6 7/9] RISC-V: Add sscofpmf extension support Atish Patra
2022-02-19  0:46 ` [v6 8/9] Documentation: riscv: Remove the old documentation Atish Patra
2022-02-19  0:47 ` Atish Patra [this message]
2022-03-12  7:51 ` [v6 0/9] Improve RISC-V Perf support using SBI PMU and sscofpmf extension Nikita Shubin
2022-03-21 23:57 ` Palmer Dabbelt

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=20220219004700.1973682-10-atishp@rivosinc.com \
    --to=atishp@rivosinc.com \
    --cc=anup@brainfault.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=atishp@atishpatra.org \
    --cc=damien.lemoal@wdc.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jszhang@kernel.org \
    --cc=krzysztof.kozlowski@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=robh+dt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox