All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eddie James <eajames@linux.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: gregkh@linuxfoundation.org, eajames@linux.ibm.com, jk@ozlabs.org,
	joel@jms.id.au, alistair@popple.id.au,
	linux-fsi@lists.ozlabs.org
Subject: [PATCH] MAINTAINERS: change maintainer for FSI
Date: Wed, 12 Feb 2025 11:08:27 -0600	[thread overview]
Message-ID: <20250212170827.1477102-1-eajames@linux.ibm.com> (raw)

Due to job transitions, both Joel and Jeremy can no longer maintain
the FSI subsystem. I will take over.
I also removed the link to Joel's FSI tree as he won't be maintaining
it.

Signed-off-by: Eddie James <eajames@linux.ibm.com>
---

Since there is no longer a tree associated with this subsystem, can we rely
on you, Greg, to merge changes to the FSI subsystem? Or will I need to create
a kernel.org account and an associated tree and send you merge requests?
Thanks.

 MAINTAINERS | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index 1f65a2a1cde5b..83024cd416143 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -9441,14 +9441,13 @@ F:	include/linux/fscrypt.h
 F:	include/uapi/linux/fscrypt.h
 
 FSI SUBSYSTEM
-M:	Jeremy Kerr <jk@ozlabs.org>
-M:	Joel Stanley <joel@jms.id.au>
+M:	Eddie James <eajames@linux.ibm.com>
+R:	Jeremy Kerr <jk@ozlabs.org>
+R:	Joel Stanley <joel@jms.id.au>
 R:	Alistar Popple <alistair@popple.id.au>
-R:	Eddie James <eajames@linux.ibm.com>
 L:	linux-fsi@lists.ozlabs.org
 S:	Supported
 Q:	http://patchwork.ozlabs.org/project/linux-fsi/list/
-T:	git git://git.kernel.org/pub/scm/linux/kernel/git/joel/fsi.git
 F:	drivers/fsi/
 F:	include/linux/fsi*.h
 F:	include/trace/events/fsi*.h
-- 
2.43.5


             reply	other threads:[~2025-02-12 17:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-12 17:08 Eddie James [this message]
2025-02-13  1:33 ` [PATCH] MAINTAINERS: change maintainer for FSI Jeremy Kerr
2025-02-13  9:51 ` Greg KH

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=20250212170827.1477102-1-eajames@linux.ibm.com \
    --to=eajames@linux.ibm.com \
    --cc=alistair@popple.id.au \
    --cc=gregkh@linuxfoundation.org \
    --cc=jk@ozlabs.org \
    --cc=joel@jms.id.au \
    --cc=linux-fsi@lists.ozlabs.org \
    --cc=linux-kernel@vger.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.