From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Chhabilal Dangal <yogeshdangal66@gmail.com>
Cc: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
Teddy Wang <teddy.wang@siliconmotion.com>,
linux-fbdev@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/2] staging: sm750fb: remove unused #include directives
Date: Tue, 12 May 2026 07:37:35 +0200 [thread overview]
Message-ID: <2026051203-slurp-slain-7458@gregkh> (raw)
In-Reply-To: <20260512044732.56417-1-yogeshdangal66@gmail.com>
On Tue, May 12, 2026 at 10:32:31AM +0545, Chhabilal Dangal wrote:
> sm750_hw.c includes <asm/mtrr.h> under #ifdef CONFIG_MTRR, but no
> mtrr_add/mtrr_del calls exist in the file; the driver uses
> arch_phys_wc_add/arch_phys_wc_del in sm750.c instead.
>
> sm750_hw.c, sm750_accel.c, and sm750_cursor.c all include
> <linux/platform_device.h>, but none use any platform device APIs.
> This is a PCI driver.
These are statements that don't really describe anything :(
> Remove these dead includes per the TODO item to refine the code
> and remove unused code.
>
> Tested by building the full kernel and module with CONFIG_FB_SM750=m
> on x86_64:
> make -j$(nproc)
> make M=drivers/staging/sm750fb modules
You don't need to have these lines, it is assumed you test-built this.
> Signed-off-by: Chhabilal Dangal <yogeshdangal66@gmail.com>
You need a blank line before this line.
Also, your patches were not properly connected, please use a tool like
git send-email to send them out.
Also, you are doing multiple things in this patch, please, only one
logical thing per commit.
thanks,
greg k-h
prev parent reply other threads:[~2026-05-12 5:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 4:47 [PATCH v1 1/2] staging: sm750fb: remove unused #include directives Chhabilal Dangal
2026-05-12 5:37 ` Greg Kroah-Hartman [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=2026051203-slurp-slain-7458@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=sudipm.mukherjee@gmail.com \
--cc=teddy.wang@siliconmotion.com \
--cc=yogeshdangal66@gmail.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