From: Johannes Berg <johannes@sipsolutions.net>
To: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>,
briannorris@chromium.org
Cc: kvalo@kernel.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org,
Abaci Robot <abaci@linux.alibaba.com>
Subject: Re: [PATCH] mwifiex: clean up some inconsistent indenting
Date: Fri, 10 Nov 2023 22:39:54 +0100 [thread overview]
Message-ID: <c4c14b15d5e0c2e4650b50ef7ae9d8755f83900e.camel@sipsolutions.net> (raw)
In-Reply-To: <20231110083327.7022-1-jiapeng.chong@linux.alibaba.com>
On Fri, 2023-11-10 at 16:33 +0800, Jiapeng Chong wrote:
> No functional modification involved.
>
> drivers/net/wireless/marvell/mwifiex/sta_event.c:789 mwifiex_process_sta_event() warn: inconsistent indenting.
OK, sure ...
> +++ b/drivers/net/wireless/marvell/mwifiex/sta_event.c
> @@ -762,7 +762,7 @@ int mwifiex_process_sta_event(struct mwifiex_private *priv)
> mwifiex_dbg(adapter, EVENT, "info: EVENT: AWAKE\n");
> if (!adapter->pps_uapsd_mode &&
> (priv->port_open ||
> - (priv->bss_mode == NL80211_IFTYPE_ADHOC)) &&
> + (priv->bss_mode == NL80211_IFTYPE_ADHOC)) &&
> priv->media_connected && adapter->sleep_period.period) {
> adapter->pps_uapsd_mode = true;
> mwifiex_dbg(adapter, EVENT,
> @@ -773,7 +773,7 @@ int mwifiex_process_sta_event(struct mwifiex_private *priv)
> if (mwifiex_check_last_packet_indication(priv)) {
> if (adapter->data_sent ||
> (adapter->if_ops.is_port_ready &&
> - !adapter->if_ops.is_port_ready(priv))) {
> + !adapter->if_ops.is_port_ready(priv))) {
> adapter->ps_state = PS_STATE_AWAKE;
> adapter->pm_wakeup_card_req = false;
> adapter->pm_wakeup_fw_try = false;
Seems fine.
> @@ -781,12 +781,10 @@ int mwifiex_process_sta_event(struct mwifiex_private *priv)
> break;
> }
> if (!mwifiex_send_null_packet
> - (priv,
> - MWIFIEX_TxPD_POWER_MGMT_NULL_PACKET |
> - MWIFIEX_TxPD_POWER_MGMT_LAST_PACKET))
> - adapter->ps_state =
> - PS_STATE_SLEEP;
> - return 0;
> + (priv, MWIFIEX_TxPD_POWER_MGMT_NULL_PACKET |
> + MWIFIEX_TxPD_POWER_MGMT_LAST_PACKET))
> + adapter->ps_state = PS_STATE_SLEEP;
> + return 0;
>
🤷♀️️
That's not really an improvement is it? You've just indented the
function arguments as if they were part another part of the condition? I
mean, sure, it was awful - but ... maybe better break the 80 cols rule
(which isn't one any more anyway)?
johannes
next prev parent reply other threads:[~2023-11-10 21:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 8:33 Jiapeng Chong
2023-11-10 21:39 ` Johannes Berg [this message]
2023-11-11 0:38 ` Jeff Johnson
2023-11-11 0:57 ` Johannes Berg
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=c4c14b15d5e0c2e4650b50ef7ae9d8755f83900e.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=abaci@linux.alibaba.com \
--cc=briannorris@chromium.org \
--cc=jiapeng.chong@linux.alibaba.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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®