From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Russell King - ARM Linux <linux@armlinux.org.uk>,
Juerg Haefliger <juergh@canonical.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [next] Error: selected processor does not support `isb ' in ARM mode
Date: Mon, 1 Nov 2021 18:50:20 +0530 [thread overview]
Message-ID: <CA+G9fYt3EjUTF+C26x8sCRc+4R8raCDUOF03qmcwP820QEKgbg@mail.gmail.com> (raw)
In-Reply-To: <CAK8P3a1mP_ZvigBj5+pRSSf-OsvX70BSJByGfqcDjE5pXLD9Yw@mail.gmail.com>
Hi Arnd,
On Mon, 1 Nov 2021 at 18:44, Arnd Bergmann <arnd@arndb.de> wrote:
>
> On Mon, Nov 1, 2021 at 2:00 PM Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
> >
> > [Please ignore this email report if it is already reported]
> >
> > Regression found on arm gcc-11 built with following config
> > Following build warnings / errors reported on linux next-20211101.
> >
> > metadata:
> > git_describe: next-20211101
> > git_repo: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> > git_short_log: 9febf1194306 (\"Add linux-next specific files for 20211101\")
> > target_arch: arm
> > toolchain: gcc-11
>
> Is this a Debian gcc? If so, this one should fix it, I need to send
> that to Russell's
> patch tracker:
>
> https://lore.kernel.org/linux-arm-kernel/20211018140735.3714254-1-arnd@kernel.org/
>
Yes.
This is Debian gcc-11
- Naresh
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-11-01 13:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 13:00 [next] Error: selected processor does not support `isb ' in ARM mode Naresh Kamboju
2021-11-01 13:14 ` Arnd Bergmann
2021-11-01 13:20 ` Naresh Kamboju [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=CA+G9fYt3EjUTF+C26x8sCRc+4R8raCDUOF03qmcwP820QEKgbg@mail.gmail.com \
--to=naresh.kamboju@linaro.org \
--cc=arnd@arndb.de \
--cc=juergh@canonical.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=matthias.bgg@gmail.com \
--cc=sfr@canb.auug.org.au \
/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).