From: Baoquan He <bhe@redhat.com>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Rob Landley <rob@landley.net>,
akpm@linux-foundation.org, ysato@users.sourceforge.jp,
dalias@libc.org, linux-sh@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] sh: cast away __iomem to remove sparse warning
Date: Wed, 8 Jun 2022 15:52:51 +0800 [thread overview]
Message-ID: <YqBVU9oW6FfGdR9H@MiWiFi-R3L-srv> (raw)
In-Reply-To: <db5505e5-811e-0572-7614-8443c864b5e6@physik.fu-berlin.de>
On 06/08/22 at 09:05am, John Paul Adrian Glaubitz wrote:
> Hi!
>
> On 6/8/22 03:11, Baoquan He wrote:
> > I guess SuperH arch has been in status of no maintenance, however some
> > generic code change may involve correspondant ARCH change so that we
> > have to touch arch/sh/.
>
> It is actually actively maintained by Rich Felker but he is often slow to
> respond at the moment. I have already offered Rich my help and maybe we
> can work something out that I can help him with the maintenance.
Thanks, Adrian.
Maybe you can start with being a reviewer by adding yourself into
MAINTAINERS file like below. You need post below change as patch and got
Rich's ACK. Then people will add you to CC when sending patches related
to sh code. Or add yourself as maintainer directly if you have done a
lot of work on maintaining, surely need get other sh maintainers' ACK
too. Personal suggeestion.
diff --git a/MAINTAINERS b/MAINTAINERS
index a6d3bd9d2a8d..0e7ce3540eb7 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -19119,6 +19119,7 @@ F: drivers/watchdog/sunplus_wdt.c
SUPERH
M: Yoshinori Sato <ysato@users.sourceforge.jp>
M: Rich Felker <dalias@libc.org>
+R: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
L: linux-sh@vger.kernel.org
S: Maintained
Q: http://patchwork.kernel.org/project/linux-sh/list/
prev parent reply other threads:[~2022-06-08 8:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-07 1:34 [PATCH] sh: cast away __iomem to remove sparse warning Baoquan He
2022-05-30 12:09 ` Baoquan He
2022-06-07 22:56 ` Rob Landley
2022-06-08 1:11 ` Baoquan He
2022-06-08 7:05 ` John Paul Adrian Glaubitz
2022-06-08 7:52 ` Baoquan He [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=YqBVU9oW6FfGdR9H@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dalias@libc.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=lkp@intel.com \
--cc=rob@landley.net \
--cc=ysato@users.sourceforge.jp \
/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