From: Greg Ungerer <gerg@linux-m68k.org>
To: Thomas Zimmermann <tzimmermann@suse.de>, geert@linux-m68k.org
Cc: linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] m68k: Do not include <linux/fb.h>
Date: Sat, 1 Feb 2025 21:46:03 +1000 [thread overview]
Message-ID: <49ae4ee5-459d-40b6-8723-5cfa91a0777a@linux-m68k.org> (raw)
In-Reply-To: <20250131144026.310672-1-tzimmermann@suse.de>
Hi Thomas,
On 1/2/25 00:40, Thomas Zimmermann wrote:
> The m68k architecture's source files does not require <linux/fb.h>.
> Remove the include statements.
>
> Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
Looks good, thanks. I will apply to the m68knommu git tree, for-next branch,
after the current merge window closes.
Regards
Greg
> ---
> arch/m68k/kernel/setup_no.c | 1 -
> arch/m68k/kernel/uboot.c | 1 -
> 2 files changed, 2 deletions(-)
>
> diff --git a/arch/m68k/kernel/setup_no.c b/arch/m68k/kernel/setup_no.c
> index c926da9d5ec28..f9872098f5ca5 100644
> --- a/arch/m68k/kernel/setup_no.c
> +++ b/arch/m68k/kernel/setup_no.c
> @@ -21,7 +21,6 @@
> #include <linux/sched.h>
> #include <linux/delay.h>
> #include <linux/interrupt.h>
> -#include <linux/fb.h>
> #include <linux/module.h>
> #include <linux/mm.h>
> #include <linux/console.h>
> diff --git a/arch/m68k/kernel/uboot.c b/arch/m68k/kernel/uboot.c
> index 8bb1cb3a7490e..5e52ea150d5cb 100644
> --- a/arch/m68k/kernel/uboot.c
> +++ b/arch/m68k/kernel/uboot.c
> @@ -10,7 +10,6 @@
> #include <linux/sched.h>
> #include <linux/delay.h>
> #include <linux/interrupt.h>
> -#include <linux/fb.h>
> #include <linux/module.h>
> #include <linux/mm.h>
> #include <linux/console.h>
next prev parent reply other threads:[~2025-02-01 11:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 14:40 [PATCH] m68k: Do not include <linux/fb.h> Thomas Zimmermann
2025-02-01 11:46 ` Greg Ungerer [this message]
2025-02-01 12:16 ` John Paul Adrian Glaubitz
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=49ae4ee5-459d-40b6-8723-5cfa91a0777a@linux-m68k.org \
--to=gerg@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=tzimmermann@suse.de \
/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