DPDK patches and discussions
 help / color / mirror / Atom feed
From: Harman Kalra <hkalra@marvell.com>
To: <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>
Cc: <stephen@networkplumber.org>, <jgrajcia@cisco.com>,
	<david.marchand@redhat.com>, <anatoly.burakov@intel.com>,
	<cunming.liang@intel.com>, <jianfeng.tan@intel.com>,
	<ndabilpuram@marvell.com>, <jia.guo@intel.com>,
	<danny.zhou@intel.com>, <jblunck@infradead.org>,
	<nelio.laranjeiro@6wind.com>, <bluca@debian.org>,
	<shahafs@mellanox.com>, Harman Kalra <hkalra@marvell.com>
Subject: [dpdk-dev] [PATCH v2] maintainers: update for interrupt subsystem
Date: Wed, 17 Jun 2020 17:50:25 +0530	[thread overview]
Message-ID: <1592396425-31240-1-git-send-email-hkalra@marvell.com> (raw)

updating MAINTAINERS file for interrupt subsytem.

Signed-off-by: Harman Kalra <hkalra@marvell.com>
---
V2: simplified way for covering all interrupt related files.

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

diff --git a/MAINTAINERS b/MAINTAINERS
index 816696caf..45b6c3a99 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -182,7 +182,6 @@ F: app/test/test_cycles.c
 F: app/test/test_debug.c
 F: app/test/test_eal*
 F: app/test/test_errno.c
-F: app/test/test_interrupts.c
 F: app/test/test_logs.c
 F: app/test/test_memcpy*
 F: app/test/test_per_lcore.c
@@ -223,6 +222,11 @@ F: app/test/test_malloc.c
 F: app/test/test_memory.c
 F: app/test/test_memzone.c
 
+Interrupt Subsystem
+M: Harman Kalra <hkalra@marvell.com>
+F: lib/librte_eal/*/*interrupts.*
+F: app/test/test_interrupts.c
+
 Keep alive
 F: lib/librte_eal/include/rte_keepalive.h
 F: lib/librte_eal/common/rte_keepalive.c
-- 
2.18.0


                 reply	other threads:[~2020-06-17 12:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1592396425-31240-1-git-send-email-hkalra@marvell.com \
    --to=hkalra@marvell.com \
    --cc=anatoly.burakov@intel.com \
    --cc=bluca@debian.org \
    --cc=cunming.liang@intel.com \
    --cc=danny.zhou@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=jblunck@infradead.org \
    --cc=jgrajcia@cisco.com \
    --cc=jia.guo@intel.com \
    --cc=jianfeng.tan@intel.com \
    --cc=ndabilpuram@marvell.com \
    --cc=nelio.laranjeiro@6wind.com \
    --cc=shahafs@mellanox.com \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    /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;
as well as URLs for NNTP newsgroup(s).