public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel•org>
To: kernelci@groups•io, sfr@canb•auug.org.au,
	Thomas Bogendoerfer <tsbogend@alpha•franken.de>
Cc: info@kernelci•org, linux-next@vger•kernel.org,
	linux-mips@vger•kernel.org
Subject: Re: next/pending-fixes build: 205 builds: 2 failed, 203 passed, 6 errors, 40 warnings (v6.1-rc7-310-gb04468dba0c6)
Date: Mon, 5 Dec 2022 12:14:02 +0000	[thread overview]
Message-ID: <Y43gij0rJWFWFeSz@sirena.org.uk> (raw)
In-Reply-To: <20221205105718.38e244a0@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 800 bytes --]

On Mon, Dec 05, 2022 at 10:57:18AM +1100, Stephen Rothwell wrote:
> On Sun, 04 Dec 2022 15:31:59 -0800 (PST) "kernelci.org bot" <bot@kernelci•org> wrote:

> > mips:
> >     fuloong2e_defconfig (gcc-10): 1 error
> >     lemote2f_defconfig (gcc-10): 1 error
> >     loongson2k_defconfig (gcc-10): 1 error
> >     loongson3_defconfig (gcc-10): 1 error

> > Errors summary:
> > 
> >     4    cc1: error: ‘-mloongson-mmi’ must be used with ‘-mhard-float’
> >     1    arch/arm/kernel/head.S:319: Error: missing expression -- `ldr r7,=0x'
> >     1    arch/arm/kernel/head.S:319: Error: missing expression -- `ldr r3,=0x'

> These have been around for a very long time, now.  Is there some way we
> can get them fixed?

Presumably, I've added Thomas as he's the MIPS maintainer.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2022-12-05 12:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-04 23:31 next/pending-fixes build: 205 builds: 2 failed, 203 passed, 6 errors, 40 warnings (v6.1-rc7-310-gb04468dba0c6) kernelci.org bot
2022-12-04 23:57 ` Stephen Rothwell
2022-12-05 12:14   ` Mark Brown [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=Y43gij0rJWFWFeSz@sirena.org.uk \
    --to=broonie@kernel$(echo .)org \
    --cc=info@kernelci$(echo .)org \
    --cc=kernelci@groups$(echo .)io \
    --cc=linux-mips@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    --cc=tsbogend@alpha$(echo .)franken.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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