From: Imre Kaloz <kaloz@kernel.org>
To: Andreas Larsson <andreas@gaisler.com>,
"David S. Miller" <davem@davemloft.net>
Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
"Mike Rapoport (IBM)" <rppt@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, Stian Halseth <stian@itx.no>
Subject: Re: [PATCH v2 2/2] sparc64: flush vmalloc ranges from the D-cache on map and unmap
Date: Thu, 22 Oct 2026 01:31:38 +0200 [thread overview]
Message-ID: <20261021233139.27341-1-kaloz@kernel.org> (raw)
In-Reply-To: <1649afcb-ae04-406c-ac41-92f62d7343ed@gaisler.com>
Hi Andreas,
Thanks for the review!
> I would not say a cross call lands on address 0, which kind of sounds
> like execution would end up there, [...]
Agreed, reworded in v3.
> I'm afraid this solution could be a bit fragile though, [...]
Good idea, that's the new 1/4 in v3 (not for stable), and the 3/4
message now says why the filter stays.
> This is a strange email address to use for a Suggested-by
It's the GitHub noreply one and I don't have a real address, so v3
drops it and credits them through the Link instead.
> Given that this patch depends on the previous patch in the series, [...]
Done.
Best,
Imre
next prev parent reply other threads:[~2026-10-21 23:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 13:21 [PATCH v2 0/2] sparc64: D-cache alias flushing fixes Imre Kaloz
2026-09-28 13:21 ` [PATCH v2 1/2] sparc64: flush only the aliased page, not its whole folio Imre Kaloz
2026-10-15 14:46 ` Andreas Larsson
2026-10-15 19:26 ` Imre Kaloz
2026-10-17 10:34 ` John Paul Adrian Glaubitz
2026-10-21 14:14 ` Andreas Larsson
2026-10-21 23:24 ` Imre Kaloz
2026-09-28 13:21 ` [PATCH v2 2/2] sparc64: flush vmalloc ranges from the D-cache on map and unmap Imre Kaloz
2026-10-21 14:18 ` Andreas Larsson
2026-10-21 23:31 ` Imre Kaloz [this message]
2026-10-11 9:33 ` [PATCH v2 0/2] sparc64: D-cache alias flushing fixes John Paul Adrian Glaubitz
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=20261021233139.27341-1-kaloz@kernel.org \
--to=kaloz@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andreas@gaisler.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rppt@kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=stian@itx.no \
--cc=willy@infradead.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 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.