All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: "John Warthog9 Hawley" <warthog9@kernel.org>
Subject: [for-next][PATCH 7/7] ktest: Add KTEST section to MAINTAINERS file
Date: Mon, 03 May 2021 19:05:17 -0400	[thread overview]
Message-ID: <20210503230658.040275516@goodmis.org> (raw)
In-Reply-To: 20210503230510.845068955@goodmis.org

From: "Steven Rostedt (VMware)" <rostedt@goodmis.org>

As I wanted to add John Hawley as a co-maintainer for ktest, I found that
there never was a KTEST section in the MAINTAINERS file. Add one!

Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
---
 MAINTAINERS | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index d92f85ca831d..3539d76232de 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -9976,6 +9976,12 @@ S:	Maintained
 F:	Documentation/devicetree/bindings/leds/backlight/kinetic,ktd253.yaml
 F:	drivers/video/backlight/ktd253-backlight.c
 
+KTEST
+M:	Steven Rostedt <rostedt@goodmis.org>
+M:	John Hawley <warthog9@eaglescrag.net>
+S:	Maintained
+F:	tools/testing/ktest
+
 L3MDEV
 M:	David Ahern <dsahern@kernel.org>
 L:	netdev@vger.kernel.org
-- 
2.30.1



      parent reply	other threads:[~2021-05-03 23:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-03 23:05 [for-next][PATCH 0/7] ktest: Get ready for pulling for 5.13 Steven Rostedt
2021-05-03 23:05 ` [for-next][PATCH 1/7] ktest: Minor cleanup with uninitialized variable $build_options Steven Rostedt
2021-05-03 23:05 ` [for-next][PATCH 2/7] ktest: Add example config for using VMware VMs Steven Rostedt
2021-05-03 23:05 ` [for-next][PATCH 3/7] ktest: Adding editor hints to improve consistency Steven Rostedt
2021-05-03 23:05 ` [for-next][PATCH 4/7] ktest: Fixing indentation to match expected pattern Steven Rostedt
2021-05-03 23:05 ` [for-next][PATCH 5/7] ktest: Further consistency cleanups Steven Rostedt
2021-05-03 23:05 ` [for-next][PATCH 6/7] ktest: Re-arrange the code blocks for better discoverability Steven Rostedt
2021-05-03 23:05 ` Steven Rostedt [this message]

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=20210503230658.040275516@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=warthog9@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 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.