mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Thomas Huth" <thuth@redhat.com>, "Mark Brown" <broonie@kernel.org>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	linux-next <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the asm-generic tree
Date: Mon, 16 Nov 2026 10:59:31 +0100	[thread overview]
Message-ID: <43b9889e-f504-468b-af05-d62e1043edd2@app.fastmail.com> (raw)
In-Reply-To: <a2ccfd68-c773-416b-8aac-12a7f9caa801@redhat.com>

On Mon, Nov 16, 2026, at 10:55, Thomas Huth wrote:
> Am 13.11.26 um 17:16 schrieb Arnd Bergmann:

>> There was another report for the 0day build bot about the same error
>> on powerpc, but not enough information for me to reproduce, so it's
>> possible that we need another fix like this.
> I was finally able to get access to a ppc64 machine and tried to reproduce 
> the problem. But it was just the vdso_test_chacha test again that was 
> failing there due to the __ASSEMBLY__ still being used in /usr/include, i.e. 
> the same problem that we saw on aarch64. I double checked that it gets fixed 
> after applying 
> https://lore.kernel.org/lkml/20261030174323.370687-1-thuth@redhat.com/ , so 
> unless the 0day bot had a very unusal setup, I think we should be fine.

Ok, thanks for checking!

      Arnd

  reply	other threads:[~2026-11-16  9:59 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-13 15:04 Mark Brown
2026-11-13 15:45 ` Thomas Huth
2026-11-13 16:16   ` Arnd Bergmann
2026-11-16  9:55     ` Thomas Huth
2026-11-16  9:59       ` Arnd Bergmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-08-06  4:54 Stephen Rothwell
2024-08-06  6:30 ` Arnd Bergmann
2024-08-06  6:50   ` Stephen Rothwell
2022-07-20 12:36 Stephen Rothwell
2022-07-20 12:51 ` Arnd Bergmann
2022-07-21  6:57   ` Lukas Bulwahn
2019-02-19  6:36 Stephen Rothwell
2019-02-19  7:45 ` Hugo Lefeuvre
2019-02-19 10:14   ` Arnd Bergmann
2019-02-19 11:19     ` Hugo Lefeuvre
2019-02-19 14:42       ` Arnd Bergmann
2018-03-15 22:13 Stephen Rothwell
2018-03-15 22:47 ` Bin Liu
2018-03-16  8:07   ` Arnd Bergmann
2015-10-14 22:55 Stephen Rothwell
2015-10-14 23:32 ` kbuild test robot
2015-10-15  2:37   ` Stephen Rothwell
2014-11-19  7:54 Stephen Rothwell
2014-11-19  9:21 ` Arnd Bergmann
2014-09-26 10:02 Stephen Rothwell
2014-09-26 10:53 ` Will Deacon
2014-09-26 11:14   ` Arnd Bergmann
2014-09-29 22:31     ` Stephen Rothwell
2014-09-30 10:00       ` Arnd Bergmann

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=43b9889e-f504-468b-af05-d62e1043edd2@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=thuth@redhat.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

all inboxes | Powered by JetHome®