From: Ian Abbott <abbotti@mev.co.uk>
To: tawahpeggy <tawahpeggy98@gmail.com>,
H Hartley Sweeten <hsweeten@visionengravers.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
outreachy-kernel@googlegroups.com
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: Remove line to fix checkpatch error
Date: Mon, 12 Apr 2021 10:41:01 +0100 [thread overview]
Message-ID: <25a33398-483e-931c-f023-61bac56c72ef@mev.co.uk> (raw)
In-Reply-To: <20210411204933.GA3524@peggy-Lenovo-V130-15IKB>
On 11/04/2021 21:49, tawahpeggy wrote:
> remove one empty line.CHECK: Please don't use multiple blank lines
>
> Signed-off-by: tawahpeggy <tawahpeggy98@gmail.com>
>
> ---
> drivers/staging/comedi/comedi_pcmcia.mod.c | 1 -
> 1 file changed, 0 insertion(+), 1 deletion(-)
> create mode 100644 drivers/staging/comedi/comedi_pcmcia.mod.c
>
> diff --git a/drivers/staging/comedi/comedi_pcmcia.mod.c b/drivers/staging/comedi/comedi_pcmcia.mod.c
> index 0904b8765afs96..3984db1a39c8
> --- /dev/null
> +++ b/drivers/staging/comedi/comedi_pcmcia.mod.c
The .mod.c files are not really part of the Linux kernel source code.
They are generated during the kernel build process. There is no point
checking them with checkpatch.pl. If you are adding them to your git
repository, then you are doing something wrong.
--
-=( Ian Abbott <abbotti@mev.co.uk> || MEV Ltd. is a company )=-
-=( registered in England & Wales. Regd. number: 02862268. )=-
-=( Regd. addr.: S11 & 12 Building 67, Europa Business Park, )=-
-=( Bird Hall Lane, STOCKPORT, SK3 0XA, UK. || www.mev.co.uk )=-
next prev parent reply other threads:[~2021-04-12 9:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-11 20:49 [PATCH] Staging: Remove line to fix checkpatch error tawahpeggy
2021-04-12 9:30 ` Greg Kroah-Hartman
2021-04-12 9:41 ` Ian Abbott [this message]
2021-04-12 10:10 ` [Outreachy kernel] " Julia Lawall
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=25a33398-483e-931c-f023-61bac56c72ef@mev.co.uk \
--to=abbotti@mev.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=hsweeten@visionengravers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy-kernel@googlegroups.com \
--cc=tawahpeggy98@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;
as well as URLs for NNTP newsgroup(s).