public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: Paul Walmsley <pjw@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Paul Walmsley <pjw@kernel.org>,
	torvalds@linux-foundation.org,  linux-riscv@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] RISC-V updates for v7.1
Date: Fri, 24 Apr 2026 07:26:51 -0600 (MDT)	[thread overview]
Message-ID: <833360eb-6e67-053f-bb26-451e00075dbe@kernel.org> (raw)
In-Reply-To: <20260424003249.GA2985598@ax162>

Hi Nathan,

On Thu, 23 Apr 2026, Nathan Chancellor wrote:

> On Thu, Apr 23, 2026 at 06:07:29PM -0600, Paul Walmsley wrote:
> > Nam Cao (6):
> >       riscv: Clean up & optimize unaligned scalar access probe
> >       riscv: Split out measure_cycles() for reuse
> >       riscv: Reuse measure_cycles() in check_vector_unaligned_access()
> >       riscv: Split out compare_unaligned_access()
> >       riscv: Reuse compare_unaligned_access() in check_vector_unaligned_access()
> >       riscv: Remove support for XIP kernel
> 
> Please note that this series is broken with CONFIG_CFI. Please see the
> fix I sent and consider applying it sooner rather than later:
> 
>   https://lore.kernel.org/20260406-measure_cycles-cfi-failure-v1-1-03e0234ae02f@kernel.org/

Thanks very much for the reminder; queued for v7.1-rc.


- Paul

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2026-04-24 13:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-24  0:07 [GIT PULL] RISC-V updates for v7.1 Paul Walmsley
2026-04-24  0:32 ` Nathan Chancellor
2026-04-24 13:26   ` Paul Walmsley [this message]
2026-04-24 18:32 ` pr-tracker-bot

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=833360eb-6e67-053f-bb26-451e00075dbe@kernel.org \
    --to=pjw@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=nathan@kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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