From: Greg KH <gregkh@linuxfoundation.org>
To: "Isaac J. Manjarres" <isaacmanjarres@google.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
Nick Kossifidis <mick@ics.forth.gr>,
Mike Rapoport <rppt@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Saravana Kannan <saravanak@google.com>,
linux-mm@kvack.org,
"Kirill A . Shutemov" <kirill.shtuemov@linux.intel.com>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Rob Herring <robh@kernel.org>,
stable@vger.kernel.org, kernel-team@android.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5.15] of: reserved_mem: Have kmemleak ignore dynamically allocated reserved mem
Date: Sat, 18 Feb 2023 11:29:01 +0100 [thread overview]
Message-ID: <Y/CobZuHXU529cdx@kroah.com> (raw)
In-Reply-To: <20230217200731.285514-1-isaacmanjarres@google.com>
On Fri, Feb 17, 2023 at 12:07:30PM -0800, Isaac J. Manjarres wrote:
> commit ce4d9a1ea35ac5429e822c4106cb2859d5c71f3e upstream.
>
> Patch series "Fix kmemleak crashes when scanning CMA regions", v2.
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2023-02-18 10:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 20:07 [PATCH 5.15] of: reserved_mem: Have kmemleak ignore dynamically allocated reserved mem Isaac J. Manjarres
2023-02-18 10:29 ` Greg KH [this message]
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=Y/CobZuHXU529cdx@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=isaacmanjarres@google.com \
--cc=kernel-team@android.com \
--cc=kirill.shtuemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mick@ics.forth.gr \
--cc=rafael.j.wysocki@intel.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=rppt@kernel.org \
--cc=saravanak@google.com \
--cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).