From: Jeremy Kerr <jk@ozlabs.org>
To: Eddie James <eajames@linux.ibm.com>, linux-kernel@vger.kernel.org
Cc: gregkh@linuxfoundation.org, joel@jms.id.au,
alistair@popple.id.au, linux-fsi@lists.ozlabs.org
Subject: Re: [PATCH] MAINTAINERS: change maintainer for FSI
Date: Thu, 13 Feb 2025 09:33:10 +0800 [thread overview]
Message-ID: <7771db0e45a7152f42cbb45423ff9cca9a95dfd8.camel@ozlabs.org> (raw)
In-Reply-To: <20250212170827.1477102-1-eajames@linux.ibm.com>
Hi Eddie,
> Due to job transitions, both Joel and Jeremy can no longer maintain
> the FSI subsystem. I will take over.
Sounds good, thanks. Given Joel, Alistair and I no longer have hardware
access, would it make sense to remove the R: entries completely?
[I'm happy to do keep an eye on patches, but my usefulness would be
limited to cursory review]
Either way:
Acked-by: Jeremy Kerr <jk@ozlabs.org>
Cheers,
Jeremy
next prev parent reply other threads:[~2025-02-13 1:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 17:08 [PATCH] MAINTAINERS: change maintainer for FSI Eddie James
2025-02-13 1:33 ` Jeremy Kerr [this message]
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=7771db0e45a7152f42cbb45423ff9cca9a95dfd8.camel@ozlabs.org \
--to=jk@ozlabs.org \
--cc=alistair@popple.id.au \
--cc=eajames@linux.ibm.com \
--cc=gregkh@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox