From: Hans de Goede <hdegoede@redhat.com>
To: Jagath Jog J <jagathjog1996@gmail.com>,
gregkh@linuxfoundation.org, Larry.Finger@lwfinger.net
Cc: fabioaiuto83@gmail.com, dan.carpenter@oracle.com,
marcocesati@gmail.com, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [Patch 0/3] Staging: rtl8723bs: Fix codestyle errors and warnings
Date: Mon, 24 Jan 2022 09:16:08 +0100 [thread overview]
Message-ID: <7792513f-4f5a-d2b8-f142-ac14d97cda8f@redhat.com> (raw)
In-Reply-To: <20220124034456.8665-1-jagathjog1996@gmail.com>
Hi,
On 1/24/22 04:44, Jagath Jog J wrote:
> This series fix the following errors/warnings:
>
> -Placing { braces at the end of same line of if condition
> -Removed extra spaces in declaration
> -Placing necessary blank line after declaration
Thanks, series looks good to me:
Reviewed-by: Hans de Goede <hdegoede@redhat.com>
for the series.
Regards,
Hans
>
> Jagath Jog J (3):
> Staging: rtl8723bs: Placing opening { braces in previous line
> Staging: rtl8723bs: Removed extra spaces between datatype and variable
> Staging: rtl8723bs: Inserting blank line after declaration
>
> drivers/staging/rtl8723bs/core/rtw_cmd.c | 54 +++++-----
> drivers/staging/rtl8723bs/hal/hal_intf.c | 5 +
> .../staging/rtl8723bs/os_dep/ioctl_cfg80211.c | 98 ++++++-------------
> 3 files changed, 63 insertions(+), 94 deletions(-)
>
prev parent reply other threads:[~2022-01-24 8:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 3:44 Jagath Jog J
2022-01-24 3:44 ` [Patch 1/3] Staging: rtl8723bs: Placing opening { braces in previous line Jagath Jog J
2022-01-25 17:22 ` Joe Perches
2022-01-24 3:44 ` [Patch 2/3] Staging: rtl8723bs: Removed extra spaces between datatype and variable Jagath Jog J
2022-01-24 3:44 ` [Patch 3/3] Staging: rtl8723bs: Inserting blank line after declaration Jagath Jog J
2022-01-24 8:16 ` Hans de Goede [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=7792513f-4f5a-d2b8-f142-ac14d97cda8f@redhat.com \
--to=hdegoede@redhat.com \
--cc=Larry.Finger@lwfinger.net \
--cc=dan.carpenter@oracle.com \
--cc=fabioaiuto83@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jagathjog1996@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=marcocesati@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
all inboxes | Powered by JetHome®