From: David Miller <davem@redhat.com>
To: masahiroy@kernel.org
Cc: linux-kbuild@vger.kernel.org, sparclinux@vger.kernel.org,
arnd@arndb.de, bcollins@debian.org, michal.lkml@markovi.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] modpost: assume STT_SPARC_REGISTER is defined
Date: Mon, 06 Jan 2020 13:33:36 -0800 (PST) [thread overview]
Message-ID: <20200106.133336.719905028750983361.davem@redhat.com> (raw)
In-Reply-To: <20200104153651.2258-1-masahiroy@kernel.org>
From: Masahiro Yamada <masahiroy@kernel.org>
Date: Sun, 5 Jan 2020 00:36:51 +0900
> Commit 8d5290149ee1 ("[SPARC]: Deal with glibc changing macro names in
> modpost.c") was more than 14 years ago. STT_SPARC_REGISTER is hopefully
> defined in elf.h of recent C libraries.
>
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Acked-by: David S. Miller <davem@davemloft.net>
next prev parent reply other threads:[~2020-01-06 21:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-04 15:36 [PATCH] modpost: assume STT_SPARC_REGISTER is defined Masahiro Yamada
2020-01-06 21:33 ` David Miller [this message]
2020-01-11 7:26 ` Masahiro Yamada
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=20200106.133336.719905028750983361.davem@redhat.com \
--to=davem@redhat.com \
--cc=arnd@arndb.de \
--cc=bcollins@debian.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=sparclinux@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