From: Nathan Chancellor <nathan@kernel.org>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
Arnd Bergmann <arnd@arndb.de>, Ard Biesheuvel <ardb@kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH v4 2/4] ARM: use .arch directives instead of assembler command line flags
Date: Tue, 8 Nov 2022 11:40:28 -0700 [thread overview]
Message-ID: <Y2qinCG/Bmq9zGCK@dev-arch.thelio-3990X> (raw)
In-Reply-To: <Y2qhzhgLIiDD0EI9@shell.armlinux.org.uk>
On Tue, Nov 08, 2022 at 06:37:02PM +0000, Russell King (Oracle) wrote:
> On Tue, Nov 08, 2022 at 11:30:39AM -0700, Nathan Chancellor wrote:
> > I noticed that this series appears to be partially applied in
> > next-20221108:
> >
> > 59247fe730db ARM: 9265/1: pass -march= only to compiler
> > bc21212c5564 ARM: 9264/1: only use -mtp=cp15 for the compiler
> > 5aa4860eb50f ARM: 9262/1: remove lazy evaluation in Makefile
> >
> > This patch (submitted as 9263/1) is needed by 9265/1; without it, builds
> > are going to break:
> >
> > https://builds.tuxbuild.com/2HGSpQMAKxJuaMAz2ZZc1UgUvvu/build.log
> >
> > Was there a problem with applying this patch or just an oversight? It
> > would be great to get this whole series applied so that we can turn
> > -Wunused-command-line-argument into a hard error.
>
> Patching 9263/1...
> git apply --whitespace=fix -p1 --index --check > /tmp/pdb.726086 2>&1
> exited with non-zero status: 256
> error: patch failed: arch/arm/mach-mvebu/Makefile:1
> error: arch/arm/mach-mvebu/Makefile: patch does not apply
>
> The problem appears to be:
>
> 84fc86360623 ARM: make ARCH_MULTIPLATFORM user-visible
>
> which is not in my misc branch. I've applied your patch using GNU
> patch with a fuzz of 2, and the resulting diff looks sensible. I'll
> push it out later this evening.
>
> Thanks for the heads-up.
Perfect, thanks a lot for the quick response! I figured it was something
like that. I will keep an eye out for any additional breakage and follow
up with patches or additional emails as necessary.
Cheers,
Nathan
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-11-08 18:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 20:13 [PATCH v4 0/4] pass -march= only to compiler Nick Desaulniers
2022-10-14 20:13 ` [PATCH v4 1/4] ARM: remove lazy evaluation in Makefile Nick Desaulniers
2022-10-14 21:18 ` Nathan Chancellor
2022-10-14 20:13 ` [PATCH v4 2/4] ARM: use .arch directives instead of assembler command line flags Nick Desaulniers
2022-10-14 21:19 ` Nathan Chancellor
2022-11-08 18:30 ` Nathan Chancellor
2022-11-08 18:37 ` Russell King (Oracle)
2022-11-08 18:40 ` Nathan Chancellor [this message]
2022-10-14 20:13 ` [PATCH v4 3/4] ARM: only use -mtp=cp15 for the compiler Nick Desaulniers
2022-10-14 21:20 ` Nathan Chancellor
2022-10-14 20:13 ` [PATCH v4 4/4] ARM: pass -march= only to compiler Nick Desaulniers
2022-10-14 21:21 ` Nathan Chancellor
2022-10-14 20:16 ` [PATCH v4 0/4] " Nick Desaulniers
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=Y2qinCG/Bmq9zGCK@dev-arch.thelio-3990X \
--to=nathan@kernel.org \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=ndesaulniers@google.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