stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
	Sasha Levin <sashal@kernel.org>,
	linux- stable <stable@vger.kernel.org>,
	lkft-triage@lists.linaro.org
Subject: Re: stable-rc 4.9: arm: arch/arm/vfp/vfphw.S:158: Error: bad instruction `ldcleq p11,cr0,[r10],#32*4'
Date: Mon, 1 Jun 2020 19:35:10 +0200	[thread overview]
Message-ID: <20200601173510.GA1262785@kroah.com> (raw)
In-Reply-To: <20200601172135.GA1236358@kroah.com>

On Mon, Jun 01, 2020 at 07:21:35PM +0200, Greg Kroah-Hartman wrote:
> On Mon, Jun 01, 2020 at 06:07:51PM +0100, Russell King - ARM Linux admin wrote:
> > On Mon, Jun 01, 2020 at 07:02:48PM +0200, Greg Kroah-Hartman wrote:
> > > On Mon, Jun 01, 2020 at 09:18:34PM +0530, Naresh Kamboju wrote:
> > > > stable-rc 4.9 arm architecture build failed due to
> > > > following errors,
> > > > 
> > > > # make -sk KBUILD_BUILD_USER=TuxBuild -C/linux -j16 ARCH=arm
> > > > CROSS_COMPILE=arm-linux-gnueabihf- HOSTCC=gcc CC="sccache
> > > > arm-linux-gnueabihf-gcc" O=build zImage
> > > > #
> > > > ../arch/arm/vfp/vfphw.S: Assembler messages:
> > > > ../arch/arm/vfp/vfphw.S:158: Error: bad instruction `ldcleq p11,cr0,[r10],#32*4'
> > > > ../arch/arm/vfp/vfphw.S:233: Error: bad instruction `stcleq p11,cr0,[r0],#32*4'
> > > > make[2]: *** [../scripts/Makefile.build:404: arch/arm/vfp/vfphw.o] Error 1
> > > > make[2]: Target '__build' not remade because of errors.
> > > > make[1]: *** [/linux/Makefile:1040: arch/arm/vfp] Error 2
> > > > ../arch/arm/lib/changebit.S: Assembler messages:
> > > > ../arch/arm/lib/changebit.S:15: Error: bad instruction `strbne r1,[ip]'
> > 
> > It looks like Naresh's toolchain doesn't like the new format
> > instructions.  Which toolchain (and versions of the individual
> > tools) are you (Naresh) using?
> > 
> > > Odd, I'll drop it from 4.9, but it's also in the 4.14 and 4.19 queues as
> > > well, is it causing issues there too?
> > 
> > What if it turns out that Naresh is using an ancient toolchain
> > that isn't supported by these kernels?  Does that still count as
> > a reason to drop the patch?
> 
> Depends on if anyone actually wants to use the newer toolchain on the
> really-old 4.9 release :)

Ok, looks like other patches in the queue depended on this one, so I've
added it back, and we can figure out what Naresh's toolchain is here...

thanks,

greg k-h

  reply	other threads:[~2020-06-01 17:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-01 15:48 stable-rc 4.9: arm: arch/arm/vfp/vfphw.S:158: Error: bad instruction `ldcleq p11,cr0,[r10],#32*4' Naresh Kamboju
2020-06-01 17:02 ` Greg Kroah-Hartman
2020-06-01 17:07   ` Russell King - ARM Linux admin
2020-06-01 17:21     ` Greg Kroah-Hartman
2020-06-01 17:35       ` Greg Kroah-Hartman [this message]
2020-06-01 17:38         ` Naresh Kamboju
2020-06-01 17:31     ` Naresh Kamboju
2020-06-01 18:26       ` Sasha Levin
2020-06-01 18:33         ` Naresh Kamboju
2020-06-01 18:29       ` Russell King - ARM Linux admin
2020-06-01 19:45         ` Naresh Kamboju
2020-06-01 20:37           ` Russell King - ARM Linux admin

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=20200601173510.GA1262785@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux@armlinux.org.uk \
    --cc=lkft-triage@lists.linaro.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=sashal@kernel.org \
    --cc=stable@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;
as well as URLs for NNTP newsgroup(s).