From: Mike Rapoport <rppt@kernel.org>
To: Karolina Drobnik <karolinadrobnik@gmail.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Matthew Wilcox <willy@infradead.org>
Subject: Re: [PATCH] memblock: Remove unused io.h include
Date: Tue, 1 Feb 2022 17:26:29 +0200 [thread overview]
Message-ID: <YflRJZV94Mx6lKAG@kernel.org> (raw)
In-Reply-To: <20220131121723.72395-1-karolinadrobnik@gmail.com>
Hi Karolina,
On Mon, Jan 31, 2022 at 01:17:23PM +0100, Karolina Drobnik wrote:
> Memblock does not use anything from io.h, remove the include.
As Matthew pointed out [1], many architectures put their definition of
virt_to_phys() in asm/io.h, e.g.
arch/powerpc/include/asm/io.h:#define virt_to_phys virt_to_phys
arch/sh/include/asm/io.h:#define virt_to_phys(address) ((unsigned long)(address))
arch/x86/include/asm/io.h:#define virt_to_phys virt_to_phys
which means memblock needs this header for declaration of virt_to_phys().
Although it is included indirectly, let's keep it for now.
[1] https://lore.kernel.org/all/YfbQlMyohx31FhSW@casper.infradead.org/
> Suggested-by: Matthew Wilcox (Oracle) <willy@infradead.org>
> Signed-off-by: Karolina Drobnik <karolinadrobnik@gmail.com>
> ---
> mm/memblock.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/mm/memblock.c b/mm/memblock.c
> index 1018e50566f3..4ee190b3f026 100644
> --- a/mm/memblock.c
> +++ b/mm/memblock.c
> @@ -18,7 +18,6 @@
> #include <linux/memblock.h>
>
> #include <asm/sections.h>
> -#include <linux/io.h>
>
> #include "internal.h"
>
> --
> 2.30.2
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2022-02-01 15:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 12:17 Karolina Drobnik
2022-02-01 15:26 ` Mike Rapoport [this message]
2022-02-02 8:43 ` Karolina Drobnik
2022-02-02 14:06 ` Christoph Hellwig
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=YflRJZV94Mx6lKAG@kernel.org \
--to=rppt@kernel.org \
--cc=karolinadrobnik@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox