From: Masahiro Yamada <masahiroy@kernel.org>
To: Paul Cercueil <paul@crapouillou.net>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
"open list:BROADCOM NVRAM DRIVER" <linux-mips@vger.kernel.org>,
Alexander Lobakin <alobakin@pm.me>, Arnd Bergmann <arnd@arndb.de>,
Xingxing Su <suxingxing@loongson.cn>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
zhaoxiao <zhaoxiao@uniontech.com>
Subject: Re: [PATCH] mips: decompressor: do not copy source files while building
Date: Wed, 10 Nov 2021 01:57:28 +0900 [thread overview]
Message-ID: <CAK7LNAQzUDerTOpaNjSSRAWqwQHC8RY2MX3VeEk_uJS9AXK82w@mail.gmail.com> (raw)
In-Reply-To: <YG0B2R.AN2GMAOFSVCK1@crapouillou.net>
On Tue, Nov 9, 2021 at 9:10 PM Paul Cercueil <paul@crapouillou.net> wrote:
>
> Hi Masahiro,
>
> Le ven., nov. 5 2021 at 11:38:14 +0900, Masahiro Yamada
> <masahiroy@kernel.org> a écrit :
> > As commit 7ae4a78daacf ("ARM: 8969/1: decompressor: simplify libfdt
> > builds") stated, copying source files during the build time may not
> > end up with as clean code as expected.
> >
> > Do similar for mips to clean up the Makefile and .gitignore.
>
> What did you base this patch on?
>
> It does not apply cleanly here. It tries to create ashldi3.c and
> bswapsi.c, which already exist.
>
Please remove them manually
before 'git am'.
--
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2021-11-09 16:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 2:38 [PATCH] mips: decompressor: do not copy source files while building Masahiro Yamada
2021-11-09 12:10 ` Paul Cercueil
2021-11-09 16:57 ` Masahiro Yamada [this message]
2021-11-09 20:28 ` Paul Cercueil
2021-11-10 8:49 ` Thomas Bogendoerfer
2021-11-10 17:02 ` Masahiro Yamada
2021-11-10 18:52 ` Thomas Bogendoerfer
2021-11-11 2:58 ` Masahiro Yamada
2021-11-11 7:55 ` Masahiro Yamada
2021-11-11 8:14 ` Thomas Bogendoerfer
2021-11-11 8:24 ` 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=CAK7LNAQzUDerTOpaNjSSRAWqwQHC8RY2MX3VeEk_uJS9AXK82w@mail.gmail.com \
--to=masahiroy@kernel.org \
--cc=alobakin@pm.me \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paul@crapouillou.net \
--cc=suxingxing@loongson.cn \
--cc=tsbogend@alpha.franken.de \
--cc=zhaoxiao@uniontech.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).