From: Dan Carpenter <dan.carpenter@linaro.org>
To: Gus Stoermer <gstoermer1@gmail.com>
Cc: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs: fix checkpatch warnings in os_dep/osdep_service.c
Date: Thu, 29 Jan 2026 10:20:27 +0300 [thread overview]
Message-ID: <aXsKO8F9vmdrBK68@stanley.mountain> (raw)
In-Reply-To: <CABm+q84v7jvq-kF4v7U3bQZjdQJS946FTGowSAGPjk5FY_LKpA@mail.gmail.com>
On Wed, Jan 28, 2026 at 06:28:59PM +0000, Gus Stoermer wrote:
> >From 64ab45283c7e006c3420242e0f7b00acc1c3fd38 Mon Sep 17 00:00:00 2001
> From: xlumen1 <gstoermer1@gmail.com>
> Date: Wed, 28 Jan 2026 18:08:46 +0000
> Subject: [PATCH] staging: rtl8723bs: fix checkpatch warnings in
> os_dep/osdep_service.c
>
> Signed-off-by: xlumen1 <gstoermer1@gmail.com>
> ---
Please use your real name. No commit message. The patch is corrupted.
You're doing too many things in one patch. Fix one type of warning at
a time.
regards,
dan carpenter
prev parent reply other threads:[~2026-01-29 7:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 18:28 [PATCH] staging: rtl8723bs: fix checkpatch warnings in os_dep/osdep_service.c Gus Stoermer
2026-01-29 7:20 ` Dan Carpenter [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=aXsKO8F9vmdrBK68@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=gstoermer1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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