public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: "Kroah-Hartman, Greg" <gregkh@linuxfoundation.org>
To: Clark Williams <williams@redhat.com>
Cc: stable-rt <stable-rt@vger.kernel.org>,
	stable <stable@vger.kernel.org>, "Claudio R.,
	Luis" <lgoncalv@redhat.com>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: Re: CI build failure in v6.6-rt
Date: Sat, 3 Aug 2024 08:20:16 +0200	[thread overview]
Message-ID: <2024080344-division-undertook-4905@gregkh> (raw)
In-Reply-To: <CAMLffL9t0SFkO90d6pFZAwp-WVbont7NgELx_WW-GRRYkF_QXA@mail.gmail.com>

On Fri, Aug 02, 2024 at 08:46:55PM +0000, Clark Williams wrote:
> Greg,
> 
> Kernel CI is reporting a build failure on v6.6-rt:
> 
> https://grafana.kernelci.org/d/build/build?orgId=1&var-datasource=default&var-build_architecture=riscv&var-build_config_name=defconfig&var-id=maestro:66a6b448bb1dfd36a925ebef
> 
> It's in arch/riscv/kernel/cpufeature.c where a return statement in
> check_unaligned_access() doesn't have a value (and
> check_unaligned_access returns int).
> 
> Is 6.6 stable supporting RiscV? If so then we either have to fix that
> return, or backport the refactor of arch/riscv/kernel/cpufeature.c
> (f413aae96cda0).  If it's not then who should I talk to about turning
> off riscv CI builds for v6.6-rt?

Why not ask the people responsible for the -rt patchset?  If this isn't
an issue on a non-rt kernel, then I think you found the problem :)

thanks,

greg k-h

  reply	other threads:[~2024-08-03  6:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-02 20:46 CI build failure in v6.6-rt Clark Williams
2024-08-03  6:20 ` Kroah-Hartman, Greg [this message]
2024-08-05 10:58   ` Sebastian Andrzej Siewior

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=2024080344-division-undertook-4905@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=bigeasy@linutronix.de \
    --cc=lgoncalv@redhat.com \
    --cc=stable-rt@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=williams@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