From: Rob Landley <rob@landley.net>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Rich Felker <dalias@libc.org>
Cc: Linux-sh list <linux-sh@vger.kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: Stalled patches for the SH tree
Date: Thu, 29 Jul 2021 11:11:12 -0500 [thread overview]
Message-ID: <be89052d-bd6f-90e5-198a-e8919fabf7ba@landley.net> (raw)
In-Reply-To: <3a14d8c5-45e4-84dc-32b9-0bb573ebc77a@physik.fu-berlin.de>
On 7/29/21 3:58 AM, John Paul Adrian Glaubitz wrote:
> Hi!
>
> I was wondering whether there is anything I can do to help with the stalled
> patches for SH? There have been a number of patches with improvements that
> were sent to the list and I think we should pick these up, also not to discourage
> external contributors in helping us maintain the SuperH port.
The main thing is collect and track the patches, and then point us at the list
of ones you think we should review.
The ones I've seen go by here recently were all part of multi-architecture
series, which I assumed would go upstream as part of the series and they were
mostly checking to see if we objected? What did I miss?
Rob
prev parent reply other threads:[~2021-07-29 15:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-29 8:58 Stalled patches for the SH tree John Paul Adrian Glaubitz
2021-07-29 16:11 ` Rob Landley [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=be89052d-bd6f-90e5-198a-e8919fabf7ba@landley.net \
--to=rob@landley.net \
--cc=dalias@libc.org \
--cc=geert@linux-m68k.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-sh@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;
as well as URLs for NNTP newsgroup(s).