From: <Conor.Dooley@microchip.com>
To: <sfr@canb.auug.org.au>, <linux-next@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Aug 12
Date: Fri, 12 Aug 2022 07:08:09 +0000 [thread overview]
Message-ID: <6c2133bc-dda4-3913-f03d-10722c2220fa@microchip.com> (raw)
In-Reply-To: <20220812121512.2164b5b1@canb.auug.org.au>
On 12/08/2022 03:15, Stephen Rothwell wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> linux-next: Tree for Aug 12
FWIW, C=1 builds with sparse for RISC-V are broken today:
CHECK ../scripts/mod/empty.c
invalid argument to '-march': '_zihintpause'
make[2]: *** [../scripts/Makefile.build:250: scripts/mod/empty.o] Error 1
make[2]: *** Deleting file 'scripts/mod/empty.o'
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [/mnt/automation/corp/workspace/ux-test_upstream-next-develop-cd@2/linux/Makefile:1287: prepare0] Error 2
make[1]: Leaving directory '/mnt/automation/corp/workspace/ux-test_upstream-next-develop-cd@2/linux/builddir'
make: *** [Makefile:231: __sub-make] Error 2
Reported here:
https://lore.kernel.org/linux-riscv/6d678e5c-dd16-aa54-d244-0cd09717476f@microchip.com/T/#t
Figure replying here to note it has more visibility.
Thanks,
Conor.
next prev parent reply other threads:[~2022-08-12 7:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 2:15 linux-next: Tree for Aug 12 Stephen Rothwell
2022-08-12 7:08 ` Conor.Dooley [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-08-12 8:39 Stephen Rothwell
2021-08-13 0:02 ` John Hubbard
2020-08-12 4:22 Stephen Rothwell
2019-08-12 9:31 Stephen Rothwell
2019-08-12 13:38 ` Geert Uytterhoeven
2019-08-12 21:39 ` Stephen Rothwell
2016-08-12 4:03 Stephen Rothwell
2015-08-12 13:39 Stephen Rothwell
2014-08-12 4:52 Stephen Rothwell
2013-08-12 7:05 Stephen Rothwell
2013-08-12 7:05 ` Stephen Rothwell
2011-08-12 7:13 Stephen Rothwell
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=6c2133bc-dda4-3913-f03d-10722c2220fa@microchip.com \
--to=conor.dooley@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.