From: hanyu001@208suo.com
To: stf_xl@wp.pl, helmut.schaa@googlemail.com, kvalo@kernel.org
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] net: wireless: ralink: rt2x00:
Date: Fri, 21 Jul 2023 14:29:21 +0800 [thread overview]
Message-ID: <3620e0bc76d3715cb8aecb0c7874390e@208suo.com> (raw)
In-Reply-To: <tencent_5118A9715146B132F423C8C9B6A3237C9E05@qq.com>
Fix checkpatch warnings:"foo* bar" should be "foo *bar"
./drivers/net/wireless/ralink/rt2x00/rt2x00.h:386: ERROR: "foo* bar"
should be "foo *bar"
./drivers/net/wireless/ralink/rt2x00/rt2x00.h:513: ERROR: "foo* bar"
should be "foo *bar"
Signed-off-by: Yu Han <hanyu001@208suo.com>
---
drivers/net/wireless/ralink/rt2x00/rt2x00.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/wireless/ralink/rt2x00/rt2x00.h
b/drivers/net/wireless/ralink/rt2x00/rt2x00.h
index 07a6a5a..c883d7f 100644
--- a/drivers/net/wireless/ralink/rt2x00/rt2x00.h
+++ b/drivers/net/wireless/ralink/rt2x00/rt2x00.h
@@ -383,7 +383,7 @@ struct rt2x00_intf {
atomic_t seqno;
};
-static inline struct rt2x00_intf* vif_to_intf(struct ieee80211_vif
*vif)
+static inline struct rt2x00_intf *vif_to_intf(struct ieee80211_vif
*vif)
{
return (struct rt2x00_intf *)vif->drv_priv;
}
@@ -510,7 +510,7 @@ struct rt2x00_sta {
int wcid;
};
-static inline struct rt2x00_sta* sta_to_rt2x00_sta(struct ieee80211_sta
*sta)
+static inline struct rt2x00_sta *sta_to_rt2x00_sta(struct ieee80211_sta
*sta)
{
return (struct rt2x00_sta *)sta->drv_priv;
}
parent reply other threads:[~2023-07-21 6:29 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <tencent_5118A9715146B132F423C8C9B6A3237C9E05@qq.com>]
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=3620e0bc76d3715cb8aecb0c7874390e@208suo.com \
--to=hanyu001@208suo.com \
--cc=helmut.schaa@googlemail.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=stf_xl@wp.pl \
/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®