public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Ross Stutterheim <ross.sweng@gmail.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Ross Stutterheim <ross.stutterheim@garmin.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, 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 16:48:06 +0100	[thread overview]
Message-ID: <Z__RNhf5CJrbv5yb@shell.armlinux.org.uk> (raw)
In-Reply-To: <c7db6fda-bf4e-4d6b-8cca-db82c40ce1b6@gmail.com>

On Wed, Apr 16, 2025 at 08:57:09AM -0500, Ross Stutterheim wrote:
> 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).

Thanks, seems all good, applied and pushed out. I'll send it to Linus
tomorrow as it's certainly a serious regression.

I'm surprised Mike hasn't responded...

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!

  reply	other threads:[~2025-04-16 15:48 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
2025-04-16 15:48       ` Russell King (Oracle) [this message]
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=Z__RNhf5CJrbv5yb@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=catalin.marinas@arm.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ross.stutterheim@garmin.com \
    --cc=ross.sweng@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox