From: Nam Cao <namcao@linutronix.de>
To: Michael Straube <straube.linux@gmail.com>
Cc: gregkh@linuxfoundation.org, philipp.g.hortmann@gmail.com,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] staging: rtl8192e: remove unnecessary line breaks
Date: Sun, 26 May 2024 16:33:42 +0200 [thread overview]
Message-ID: <20240526143342.tPBauUTi@linutronix.de> (raw)
In-Reply-To: <20240526111928.14574-3-straube.linux@gmail.com>
On Sun, May 26, 2024 at 01:19:27PM +0200, Michael Straube wrote:
> Remove some unnecessary line breaks after '=' and '==' to improve
> readability.
>
> Signed-off-by: Michael Straube <straube.linux@gmail.com>
> ---
> drivers/staging/rtl8192e/rtl8192e/rtl_dm.c | 24 ++++++++--------------
> 1 file changed, 8 insertions(+), 16 deletions(-)
>
> diff --git a/drivers/staging/rtl8192e/rtl8192e/rtl_dm.c b/drivers/staging/rtl8192e/rtl8192e/rtl_dm.c
> index 2fda44c5a412..5392d2daf870 100644
> --- a/drivers/staging/rtl8192e/rtl8192e/rtl_dm.c
> +++ b/drivers/staging/rtl8192e/rtl8192e/rtl_dm.c
> @@ -1392,8 +1392,7 @@ static void _rtl92e_dm_rx_path_sel_byrssi(struct net_device *dev)
> continue;
>
> rf_num++;
> - cur_cck_pwdb =
> - dm_rx_path_sel_table.cck_pwdb_sta[i];
> + cur_cck_pwdb = dm_rx_path_sel_table.cck_pwdb_sta[i];
>
> if (rf_num == 1) {
> cck_rx_ver2_max_index = i;
> @@ -1412,27 +1411,20 @@ static void _rtl92e_dm_rx_path_sel_byrssi(struct net_device *dev)
> }
> } else {
> if (cur_cck_pwdb > tmp_cck_max_pwdb) {
> - tmp_cck_sec_pwdb =
> - tmp_cck_max_pwdb;
> - cck_rx_ver2_sec_index =
> - cck_rx_ver2_max_index;
> + tmp_cck_sec_pwdb = tmp_cck_max_pwdb;
> + cck_rx_ver2_sec_index = cck_rx_ver2_max_index;
> tmp_cck_max_pwdb = cur_cck_pwdb;
> cck_rx_ver2_max_index = i;
> - } else if (cur_cck_pwdb ==
> - tmp_cck_max_pwdb) {
> + } else if (cur_cck_pwdb == tmp_cck_max_pwdb) {
> tmp_cck_sec_pwdb = cur_cck_pwdb;
> cck_rx_ver2_sec_index = i;
> } else if (PWDB_IN_RANGE) {
> tmp_cck_sec_pwdb = cur_cck_pwdb;
> cck_rx_ver2_sec_index = i;
> - } else if (cur_cck_pwdb ==
> - tmp_cck_sec_pwdb) {
> - if (tmp_cck_sec_pwdb ==
> - tmp_cck_min_pwdb) {
> - tmp_cck_sec_pwdb =
> - cur_cck_pwdb;
> - cck_rx_ver2_sec_index =
> - i;
> + } else if (cur_cck_pwdb == tmp_cck_sec_pwdb) {
> + if (tmp_cck_sec_pwdb == tmp_cck_min_pwdb) {
> + tmp_cck_sec_pwdb = cur_cck_pwdb;
> + cck_rx_ver2_sec_index = i;
> }
> } else if ((cur_cck_pwdb < tmp_cck_sec_pwdb) &&
> (cur_cck_pwdb > tmp_cck_min_pwdb)) {
Reviewed-by: Nam Cao <namcao@linutronix.de>
Best regards,
Nam
next prev parent reply other threads:[~2024-05-26 14:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-26 11:19 [PATCH 0/3] staging: rtl8192e: some refactoring Michael Straube
2024-05-26 11:19 ` [PATCH 1/3] staging: rtl8192e: reduce indentation level Michael Straube
2024-05-26 14:23 ` Nam Cao
2024-05-26 11:19 ` [PATCH 2/3] staging: rtl8192e: remove unnecessary line breaks Michael Straube
2024-05-26 14:33 ` Nam Cao [this message]
2024-05-26 11:19 ` [PATCH 3/3] staging: rtl8192e: remove dead code Michael Straube
2024-05-26 14:31 ` Nam Cao
2024-05-27 4:36 ` Michael Straube
2024-05-27 7:39 ` Dan Carpenter
2024-05-27 8:34 ` Michael Straube
2024-05-27 8:51 ` Dan Carpenter
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=20240526143342.tPBauUTi@linutronix.de \
--to=namcao@linutronix.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=philipp.g.hortmann@gmail.com \
--cc=straube.linux@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