From: "Michal Suchánek" <msuchanek@suse.de>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Philipp Rudo <prudo@linux.ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: allmodconfig not working with dummy-tools
Date: Thu, 8 Apr 2021 12:11:40 +0200 [thread overview]
Message-ID: <20210408101140.GK15381@kitsune.suse.cz> (raw)
In-Reply-To: <20210403104302.GX6564@kitsune.suse.cz>
On Sat, Apr 03, 2021 at 12:43:02PM +0200, Michal Suchánek wrote:
> Hello,
>
> thanks for the fix.
>
> On Fri, Apr 02, 2021 at 01:26:38AM +0900, Masahiro Yamada wrote:
> > On Thu, Apr 1, 2021 at 9:39 PM Michal Suchánek <msuchanek@suse.de> wrote:
> > I squashed the following. Please wait for tomorrow's linux-next.
>
> > diff --git a/scripts/dummy-tools/gcc b/scripts/dummy-tools/gcc
> > index 39e65fee59bd..f6d543725f1e 100755
> > --- a/scripts/dummy-tools/gcc
> > +++ b/scripts/dummy-tools/gcc
> > @@ -67,6 +67,12 @@ if arg_contain -E "$@"; then
> > fi
> > fi
> >
> > +# To set CONFIG_AS_IS_GNU
> > +if arg_contain -Wa,--version "$@"; then
> > + echo "GNU assembler (scripts/dummy-tools) 2.50"
> > + exit 0
> > +fi
> > +
> > if arg_contain -S "$@"; then
> > # For scripts/gcc-x86-*-has-stack-protector.sh
> > if arg_contain -fstack-protector "$@"; then
>
> Looks like this did not make it to linux-next (0104 does not have it,
> 0204 does not exist).
The fixup still applies locally so it loooks like it is still not
upstream.
>
> Nonetheless, applying the fixup resolves the problem.
Mostly, I still get:
which: no elfedit in (./scripts/dummy-tools)
>
> Thanks
>
> Michal
prev parent reply other threads:[~2021-04-08 10:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 12:39 Michal Suchánek
2021-04-01 16:26 ` Masahiro Yamada
2021-04-03 10:43 ` Michal Suchánek
2021-04-08 10:11 ` Michal Suchánek [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=20210408101140.GK15381@kitsune.suse.cz \
--to=msuchanek@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=prudo@linux.ibm.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
all inboxes | Powered by JetHome®