From: Ross Stutterheim <ross.sweng@gmail.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
Ross Stutterheim <ross.stutterheim@garmin.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Russell King <linux@armlinux.org.uk>,
Mike Rapoport <rppt@linux.ibm.com>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v2] arm/memremap: fix arch_memremap_can_ram_remap()
Date: Wed, 16 Apr 2025 08:57:09 -0500 [thread overview]
Message-ID: <c7db6fda-bf4e-4d6b-8cca-db82c40ce1b6@gmail.com> (raw)
In-Reply-To: <Z_-B5fAhZzShX34I@arm.com>
On 4/16/25 05:09, Catalin Marinas wrote:
>> Fixes: 260364d112bc ("arm[64]/memremap: don't abuse pfn_valid() to ensure presence of linear map")
>> Signed-off-by: Ross Stutterheim <ross.stutterheim@garmin.com>
>
> I think you could also add:
>
> Cc: <stable@vger.kernel.org>
Done. I also added some other Cc: entries on V3 along with Reviewed-by:
lines . I'm new here, so I'm not sure I've used those 100% properly.
> Not sure how Russell picks patches up these days (I used to send them to
> the patch system -
> https://www.arm.linux.org.uk/developer/patches/info.php).
>
> It might be simpler with git send-email (that's the alias I had):
>
> git send-email --add-header="KernelVersion: $(git describe --abbrev=0)" --no-thread --suppress-cc=all --to="patches@armlinux.org.uk"
>
Thanks. I created an account there and submitted V3 through the web
interface (to avoid my SMTP server appending more stuff on the end).
--
Ross
next prev parent reply other threads:[~2025-04-16 15:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 13:32 [PATCH] arm[64]/memremap: fix arch_memremap_can_ram_remap() Ross Stutterheim
2025-04-14 13:49 ` Catalin Marinas
2025-04-14 14:18 ` Ross Stutterheim
2025-04-14 14:21 ` [PATCH v2] arm/memremap: " Ross Stutterheim
2025-04-16 10:09 ` Catalin Marinas
2025-04-16 13:57 ` Ross Stutterheim [this message]
2025-04-16 15:48 ` Russell King (Oracle)
2025-04-16 22:54 ` Catalin Marinas
2025-04-19 7:04 ` Mike Rapoport
2025-04-16 11:13 ` Linus Walleij
2025-04-16 13:52 ` [PATCH v3] " Ross Stutterheim
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=c7db6fda-bf4e-4d6b-8cca-db82c40ce1b6@gmail.com \
--to=ross.sweng@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=ross.stutterheim@garmin.com \
--cc=rppt@linux.ibm.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 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.