From: Yoshinori Sato <ysato@users.sourceforge.jp>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Rich Felker <dalias@libc.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Andy Lutomirski <luto@kernel.org>,
clang-built-linux <clang-built-linux@googlegroups.com>,
Linux-sh list <linux-sh@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] sh: vsyscall: drop unnecessary cc-ldoption
Date: Sun, 12 May 2019 13:31:37 +0900 [thread overview]
Message-ID: <87sgtkqonq.wl-ysato@users.sourceforge.jp> (raw)
In-Reply-To: <fd075ea4-5fc9-a015-e4ae-180451f9bea0@physik.fu-berlin.de>
On Thu, 09 May 2019 17:44:45 +0900,
John Paul Adrian Glaubitz wrote:
>
> Hi Masahiro!
>
> On 5/9/19 9:07 AM, Masahiro Yamada wrote:
> >> So, if in doubt, there are folks in Debian which can test your kernel patch
> >> if you fear that it breaks something.
> >
> > Thanks for taking care of them in Debian.
> >
> > I am talking about the sh sub-system in the kernel here.
>
> Yes, I'm aware of that :).
>
> > SH patches occasionally fly around in LKML, but
> > the SH maintainers are not picking up them these days.
>
> Rich was normally the one maintaining the SH tree and collecting the patches,
> not sure whether he is still active. It's been a while since he sent Linus
> a pull request.
>
> Sato-san was recently a patch himself, but I think he doesn't have a tree
> himself.
>
> @Sato: Could you have a look at the patch and ack it if it's okay?
I sent ack now.
Sorry too late reply.
> > This one is trivial from the build system point of view.
> > So, I offer to apply it to my tree.
>
> I'm fine with that. If you need to test build the kernel for SH, Debian
> has an easily installable cross-compiler for SH and every other architecture
> except ia64 (working on fixing that) available.
>
> In any case, thanks for taking care of SH in this case.
>
> 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
--
Yosinori Sato
next prev parent reply other threads:[~2019-05-12 4:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 20:29 [PATCH] sh: require --Wl,--hash-style=sysv Nick Desaulniers
2019-04-24 6:27 ` Geert Uytterhoeven
2019-04-24 6:37 ` Masahiro Yamada
2019-04-24 6:39 ` Masahiro Yamada
2019-04-24 18:02 ` [PATCH v2] sh: vsyscall: drop unnecessary cc-ldoption Nick Desaulniers
2019-04-30 20:26 ` Nick Desaulniers
2019-05-08 19:22 ` Nick Desaulniers
2019-05-09 0:44 ` Masahiro Yamada
2019-05-09 6:09 ` John Paul Adrian Glaubitz
2019-05-09 7:07 ` Masahiro Yamada
2019-05-09 8:44 ` John Paul Adrian Glaubitz
2019-05-12 4:31 ` Yoshinori Sato [this message]
2019-05-12 4:29 ` Yoshinori Sato
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=87sgtkqonq.wl-ysato@users.sourceforge.jp \
--to=ysato@users.sourceforge.jp \
--cc=clang-built-linux@googlegroups.com \
--cc=dalias@libc.org \
--cc=geert@linux-m68k.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=luto@kernel.org \
--cc=ndesaulniers@google.com \
--cc=yamada.masahiro@socionext.com \
/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).