mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ben Dooks <ben.dooks@codethink.co.uk>
To: Paul Walmsley <pjw@kernel.org>, torvalds@linux-foundation.org
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] RISC-V updates for v6.18-rc1
Date: Tue, 30 Sep 2025 08:25:13 +0100	[thread overview]
Message-ID: <066d70c7-b0a7-45e5-9337-17901bc95664@codethink.co.uk> (raw)
In-Reply-To: <2c804359-3d43-0fba-7173-a87f9aec4bd2@kernel.org>

On 29/09/2025 09:00, Paul Walmsley wrote:
> Linus,
> 
> The following changes since commit a03ee11b8f850bd008226c6d392da24163dfb56e:
> 
>    riscv: Fix sparse warning about different address spaces (2025-09-05 15:33:52 -0600)


Is there any chance some of the big-endian work we did is getting in
for this round?

-- 
Ben Dooks				http://www.codethink.co.uk/
Senior Engineer				Codethink - Providing Genius

https://www.codethink.co.uk/privacy.html

  parent reply	other threads:[~2025-09-30  7:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-29  8:00 Paul Walmsley
2025-09-30  2:54 ` pr-tracker-bot
2025-09-30  7:25 ` Ben Dooks [this message]
2025-09-30 16:04   ` Linus Torvalds
2025-09-30 23:53     ` Linus Torvalds
2025-10-01 18:33       ` Eric Biggers
2025-10-03  1:45         ` Yury Norov
2025-10-01 19:02       ` Conor Dooley
2025-10-01 19:39         ` Linus Torvalds
2025-10-02 12:48     ` Ben Dooks
2025-10-02 15:06       ` Olof Johansson
2025-10-02 15:22         ` Ben Dooks
2025-10-07 23:43         ` Maciej W. Rozycki
2025-10-20 23:31           ` Paul Walmsley
2025-10-02 18:08       ` Theodore Ts'o
2025-10-11  8:38 ` Yao Zi

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=066d70c7-b0a7-45e5-9337-17901bc95664@codethink.co.uk \
    --to=ben.dooks@codethink.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=pjw@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

all inboxes | Powered by JetHome®