From: Dan Carpenter <dan.carpenter@oracle.com>
To: Malcolm Priestley <tvboxspy@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
Oscar Carter <oscar.carter@gmx.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/6] staging: vt6656: vnt_get_rtscts_duration_le use ieee80211_rts_duration
Date: Wed, 13 May 2020 11:07:58 +0300 [thread overview]
Message-ID: <20200513080758.GB2078@kadam> (raw)
In-Reply-To: <377a4cc3-cfe3-91aa-cf71-1063f311426a@gmail.com>
On Tue, May 05, 2020 at 10:13:54PM +0100, Malcolm Priestley wrote:
> diff --git a/drivers/staging/vt6656/rxtx.c b/drivers/staging/vt6656/rxtx.c
> index 6724b213a723..48fe16c27d3f 100644
> --- a/drivers/staging/vt6656/rxtx.c
> +++ b/drivers/staging/vt6656/rxtx.c
> @@ -285,28 +285,18 @@ static __le16 vnt_get_rtscts_duration_le(struct vnt_usb_send_context *context,
> u8 dur_type, u8 pkt_type, u16 rate)
> {
> struct vnt_private *priv = context->priv;
> - u32 cts_time = 0, dur_time = 0;
> + u32 dur_time = 0;
> u32 frame_length = context->frame_len;
> u8 need_ack = context->need_ack;
> + struct ieee80211_tx_info *info = IEEE80211_SKB_CB(context->skb);
>
> switch (dur_type) {
> + /* fall through */
> case RTSDUR_BB:
> case RTSDUR_BA:
This fall through annotation shouldn't be necessary. It's not preceded
by a case statement. Also you don't need /* fall through */ for empty
case statements. In other words you only need it for stuff like this:
case FOO:
case BAR:
frob();
frob();
/* fall through */
case BAZ:
regards,
dan carpenter
next prev parent reply other threads:[~2020-05-13 8:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 21:13 [PATCH 2/6] staging: vt6656: vnt_get_rtscts_duration_le use ieee80211_rts_duration Malcolm Priestley
2020-05-13 8:07 ` Dan Carpenter [this message]
2020-05-13 8:11 ` 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=20200513080758.GB2078@kadam \
--to=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-wireless@vger.kernel.org \
--cc=oscar.carter@gmx.com \
--cc=tvboxspy@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;
as well as URLs for NNTP newsgroup(s).