From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>, Karl Nasrallah <knnspeed@aol.com>,
Linux-SH <linux-sh@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH] sh: fixup strncpy()
Date: Mon, 1 Jun 2020 10:15:02 +0200 [thread overview]
Message-ID: <2d4ac135-3fed-a526-daf5-81d3b51197ed@physik.fu-berlin.de> (raw)
In-Reply-To: <87eeqzzn4m.wl-kuninori.morimoto.gx@renesas.com>
Hi Kuninori!
On 6/1/20 1:43 AM, Kuninori Morimoto wrote:
>> Since I don't want your fixes to fall off the table, you can ask Andrew
>> Morton to pick up your patches which is apparently the normal path to
>> choose when the original maintainers are currently not available.
>
> Actually, I had been posted it to Andrew many times [1],
> but nothing happened.
Okay, that's unfortunate.
> And according to [2], it seems SH maintainers are still working,
> thus, normal path is still them.
Yes, Rich seems to be back on track.
> I had been worked for SH before, and posted many fixup patches
> for many times to both Andrew and SH maintainers.
> But their are still not yet reviewd/accepted.
> And unfortunately, it seems I'm judged as spam from SH maintainers [2].
> So I can do nothing anymore...
I really appreciate your help and I would like to see more of your fixes
come in. Please don't be let down and let's try to get your patches
merged.
Rich has promised that he will create a new tree on his website, so I think
your patches will be merged soon.
If you have more ideas for fixes, please feel encouraged to post patches, I
will try to help you to get all of them merged. I'm very sorry that you had
to wait for such a long time.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2020-06-01 8:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 7:31 [PATCH 0/2] sh: use generic strncpy() Kuninori Morimoto
2019-12-18 7:32 ` [PATCH] " Kuninori Morimoto
2019-12-18 7:35 ` Kuninori Morimoto
2019-12-18 7:33 ` [PATCH] sh: fixup strncpy() Kuninori Morimoto
2020-05-31 9:43 ` John Paul Adrian Glaubitz
2020-05-31 23:43 ` Kuninori Morimoto
2020-06-01 8:15 ` John Paul Adrian Glaubitz [this message]
2020-06-07 12:34 ` John Paul Adrian Glaubitz
2020-06-08 0:57 ` Kuninori Morimoto
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=2d4ac135-3fed-a526-daf5-81d3b51197ed@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=dalias@libc.org \
--cc=knnspeed@aol.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).