From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: paul.walmsley@sifive.com
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Sam Ravnborg <sam@ravnborg.org>,
Michal Marek <michal.lkml@markovi.net>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Paul Walmsley <paul@pwsan.com>
Subject: Re: [PATCH v2 1/2] modpost: drop unused command line switches
Date: Wed, 21 Nov 2018 15:14:25 +0900 [thread overview]
Message-ID: <CAK7LNATQL78X2aLsAM9YQb3oCZOb+kQkB2NkoX8r=rBsH7e7mQ@mail.gmail.com> (raw)
In-Reply-To: <20181115005602.30746-2-paul.walmsley@sifive.com>
On Thu, Nov 15, 2018 at 9:56 AM Paul Walmsley <paul.walmsley@sifive.com> wrote:
>
> Drop modpost command line switches that are no longer used by
> makefile.modpost, upon request from Sam Ravnborg <sam@ravnborg.org>,
> who wrote:
>
> modpost is not supposed to be used outside the kernel build. [...]
> I checked if there were any options supported by modpost that
> was not configurable in makefile.modpost.
> And I could see that the -M and -K options in getopt() was leftovers.
> The code that used these option was was dropped in:
> commit a8773769d1a1 ("Kbuild: clear marker out of modpost")
>
> Could you add a patch that delete these on top of what you already have.
>
> https://lore.kernel.org/lkml/20181020140835.GA3351@ravnborg.org/
>
> Cc: Sam Ravnborg <sam@ravnborg.org>
> Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
> Cc: Michal Marek <michal.lkml@markovi.net>
> Cc: linux-kbuild@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> Signed-off-by: Paul Walmsley <paul.walmsley@sifive.com>
> Signed-off-by: Paul Walmsley <paul@pwsan.com>
> ---
Applied to linux-kbuild.
Thanks!
> scripts/mod/modpost.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/mod/modpost.c b/scripts/mod/modpost.c
> index 0d998c54564d..85bd93c63180 100644
> --- a/scripts/mod/modpost.c
> +++ b/scripts/mod/modpost.c
> @@ -2416,7 +2416,7 @@ int main(int argc, char **argv)
> struct ext_sym_list *extsym_iter;
> struct ext_sym_list *extsym_start = NULL;
>
> - while ((opt = getopt(argc, argv, "i:I:e:mnsST:o:awM:K:E")) != -1) {
> + while ((opt = getopt(argc, argv, "i:I:e:mnsST:o:awE")) != -1) {
> switch (opt) {
> case 'i':
> kernel_read = optarg;
> --
> 2.19.1
>
--
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2018-11-21 6:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 0:56 [PATCH v2 0/2] modpost: skip section mismatch warnings on ELF local symbols by default Paul Walmsley
2018-11-15 0:56 ` [PATCH v2 1/2] modpost: drop unused command line switches Paul Walmsley
2018-11-16 19:51 ` Sam Ravnborg
2018-11-21 6:14 ` Masahiro Yamada [this message]
2018-11-15 0:56 ` [PATCH v2 2/2] modpost: skip ELF local symbols by default during section mismatch check Paul Walmsley
2018-11-16 19:52 ` Sam Ravnborg
2018-11-21 6:13 ` Masahiro Yamada
2018-11-21 17:52 ` Paul Walmsley
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='CAK7LNATQL78X2aLsAM9YQb3oCZOb+kQkB2NkoX8r=rBsH7e7mQ@mail.gmail.com' \
--to=yamada.masahiro@socionext.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=paul.walmsley@sifive.com \
--cc=paul@pwsan.com \
--cc=sam@ravnborg.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).