From: David Hildenbrand <david@redhat.com>
To: Kevin Brodsky <kevin.brodsky@arm.com>, x86@kernel.org
Cc: linux-kernel@vger.kernel.org, bp@alien8.de,
dan.j.williams@intel.com, dave.hansen@linux.intel.com,
jane.chu@oracle.com, osalvador@suse.de, tglx@linutronix.de
Subject: Re: [PATCH v2 0/2] Remove problematic include in <asm/set_memory.h>
Date: Fri, 20 Dec 2024 11:28:51 +0100 [thread overview]
Message-ID: <c38751c0-74cf-4876-ae9e-1cc14cce5498@redhat.com> (raw)
In-Reply-To: <20241212080904.2089632-1-kevin.brodsky@arm.com>
On 12.12.24 09:09, Kevin Brodsky wrote:
> This series removes an unnecessary and potentially problematic include
> of <linux/mm.h> in <asm/set_memory.h>. There is no functional difference
> in v2 compared to v1.
>
> v1..v2:
> * Squashed include fixups into the last patch removing the include from
> <asm/set_memory.h>. [Borislav's suggestion]
> * Moved new include in <asm/smp.h>. [Borislav's suggestion]
>
> v1: https://lore.kernel.org/all/20241210184610.2080727-1-kevin.brodsky@arm.com/
>
LGTM
Acked-by: David Hildenbrand <david@redhat.com>
--
Cheers,
David / dhildenb
prev parent reply other threads:[~2024-12-20 10:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 8:09 Kevin Brodsky
2024-12-12 8:09 ` [PATCH v2 1/2] x86/mm: Remove unused __set_memory_prot() Kevin Brodsky
2025-02-28 17:03 ` [tip: x86/headers] " tip-bot2 for Kevin Brodsky
2024-12-12 8:09 ` [PATCH v2 2/2] x86/mm: Remove unnecessary include in set_memory.h Kevin Brodsky
2025-02-27 13:02 ` Ingo Molnar
2025-02-27 13:03 ` Ingo Molnar
2025-02-28 10:56 ` Kevin Brodsky
2025-02-28 17:14 ` Ingo Molnar
2025-02-28 17:43 ` Kevin Brodsky
2025-02-28 17:03 ` [tip: x86/headers] x86/mm: Reduce header dependencies in <asm/set_memory.h> tip-bot2 for Kevin Brodsky
2024-12-20 10:28 ` David Hildenbrand [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=c38751c0-74cf-4876-ae9e-1cc14cce5498@redhat.com \
--to=david@redhat.com \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=jane.chu@oracle.com \
--cc=kevin.brodsky@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=osalvador@suse.de \
--cc=tglx@linutronix.de \
--cc=x86@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
all inboxes | Powered by JetHome®