From: "Lukas Bulwahn" <lukas.bulwahn@gmail.com>
To: Milan Lakhani <milan.lakhani@codethink.co.uk>
Cc: forest@alittletooquiet.net,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-safety@lists.elisa.tech
Subject: Re: [linux-safety] [PATCH 2/2] staging: vt6655: Correct wrappping in rxtx.c
Date: Mon, 23 Nov 2020 14:17:53 +0100 [thread overview]
Message-ID: <CAKXUXMym-YfjQdDx7DcW8VHZH2bV5DbO6t0EgzmqD5hDe1AOZA@mail.gmail.com> (raw)
In-Reply-To: <1606132778-34209-2-git-send-email-milan.lakhani@codethink.co.uk>
On Mon, Nov 23, 2020 at 12:59 PM Milan Lakhani
<milan.lakhani@codethink.co.uk> wrote:
>
> Correct line length and alignment in rxtx.c. Reported by checkpatch.
>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Forest Bond <forest@alittletooquiet.net>
> CC: linux-kernel@vger.kernel.org
> CC: linux-safety@lists.elisa.tech
Milan, I am wondering where you picked up this convention to add these
Cc: and CC: tags in your patch?
Is there some documentation that points out to do that? (That might
need to be fixed...)
Did you observe that on some other commits? I think these tags are
added by some maintainers (probably tool-supported) when they pick the
patches, not by the authors, though.
> Signed-off-by: Milan Lakhani <milan.lakhani@codethink.co.uk>
> ---
> drivers/staging/vt6655/rxtx.c | 63 +++++++++++++++++++++++++++++++++----------
> 1 file changed, 49 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/staging/vt6655/rxtx.c b/drivers/staging/vt6655/rxtx.c
> index 508e1bd..4073c33 100644
> --- a/drivers/staging/vt6655/rxtx.c
> +++ b/drivers/staging/vt6655/rxtx.c
> @@ -492,14 +492,29 @@ s_uFillDataHead(
> pDevice->byTopCCKBasicRate,
> PK_TYPE_11B, &buf->b);
> /* Get Duration and TimeStamp */
> - buf->duration_a = cpu_to_le16((u16)s_uGetDataDuration(pDevice, DATADUR_A, cbFrameLength, byPktType,
> - wCurrentRate, bNeedAck, uFragIdx, cbLastFragmentSize, uMACfragNum, byFBOption));
> - buf->duration_b = cpu_to_le16((u16)s_uGetDataDuration(pDevice, DATADUR_B, cbFrameLength, PK_TYPE_11B,
> - pDevice->byTopCCKBasicRate, bNeedAck, uFragIdx, cbLastFragmentSize, uMACfragNum, byFBOption));
> - buf->duration_a_f0 = cpu_to_le16((u16)s_uGetDataDuration(pDevice, DATADUR_A_F0, cbFrameLength, byPktType,
> - wCurrentRate, bNeedAck, uFragIdx, cbLastFragmentSize, uMACfragNum, byFBOption));
> - buf->duration_a_f1 = cpu_to_le16((u16)s_uGetDataDuration(pDevice, DATADUR_A_F1, cbFrameLength, byPktType,
> - wCurrentRate, bNeedAck, uFragIdx, cbLastFragmentSize, uMACfragNum, byFBOption));
> + buf->duration_a = cpu_to_le16((u16)s_uGetDataDuration(pDevice, DATADUR_A,
> + cbFrameLength, byPktType,
> + wCurrentRate, bNeedAck,
> + uFragIdx, cbLastFragmentSize,
> + uMACfragNum, byFBOption));
> + buf->duration_b = cpu_to_le16((u16)s_uGetDataDuration(pDevice, DATADUR_B,
> + cbFrameLength, PK_TYPE_11B,
> + pDevice->byTopCCKBasicRate,
> + bNeedAck, uFragIdx,
> + cbLastFragmentSize,
> + uMACfragNum, byFBOption));
> + buf->duration_a_f0 = cpu_to_le16((u16)s_uGetDataDuration(pDevice, DATADUR_A_F0,
> + cbFrameLength, byPktType,
> + wCurrentRate, bNeedAck,
> + uFragIdx,
> + cbLastFragmentSize,
> + uMACfragNum, byFBOption));
> + buf->duration_a_f1 = cpu_to_le16((u16)s_uGetDataDuration(pDevice, DATADUR_A_F1,
> + cbFrameLength, byPktType,
> + wCurrentRate, bNeedAck,
> + uFragIdx,
> + cbLastFragmentSize,
> + uMACfragNum, byFBOption));
>
Now to this change... it seems reasonable to refactor this into a
dedicated function or macro because this is largely "copy-and-paste"
calls with slight variable on a single argument.
How about proposing such a change instead?
> buf->time_stamp_off_a = vnt_time_stamp_off(pDevice, wCurrentRate);
> buf->time_stamp_off_b = vnt_time_stamp_off(pDevice, pDevice->byTopCCKBasicRate);
> @@ -517,12 +532,32 @@ s_uFillDataHead(
> byPktType, &buf->a);
>
> /* Get Duration and TimeStampOff */
> - buf->duration = cpu_to_le16((u16)s_uGetDataDuration(pDevice, DATADUR_A, cbFrameLength, byPktType,
> - wCurrentRate, bNeedAck, uFragIdx, cbLastFragmentSize, uMACfragNum, byFBOption));
> - buf->duration_f0 = cpu_to_le16((u16)s_uGetDataDuration(pDevice, DATADUR_A_F0, cbFrameLength, byPktType,
> - wCurrentRate, bNeedAck, uFragIdx, cbLastFragmentSize, uMACfragNum, byFBOption));
> - buf->duration_f1 = cpu_to_le16((u16)s_uGetDataDuration(pDevice, DATADUR_A_F1, cbFrameLength, byPktType,
> - wCurrentRate, bNeedAck, uFragIdx, cbLastFragmentSize, uMACfragNum, byFBOption));
> + buf->duration = cpu_to_le16((u16)s_uGetDataDuration(pDevice, DATADUR_A,
> + cbFrameLength,
> + byPktType,
> + wCurrentRate, bNeedAck,
> + uFragIdx,
> + cbLastFragmentSize,
> + uMACfragNum,
> + byFBOption));
> + buf->duration_f0 = cpu_to_le16((u16)s_uGetDataDuration(pDevice,
> + DATADUR_A_F0,
> + cbFrameLength,
> + byPktType,
> + wCurrentRate,
> + bNeedAck, uFragIdx,
> + cbLastFragmentSize,
> + uMACfragNum,
> + byFBOption));
> + buf->duration_f1 = cpu_to_le16((u16)s_uGetDataDuration(pDevice,
> + DATADUR_A_F1,
> + cbFrameLength,
> + byPktType,
> + wCurrentRate,
> + bNeedAck, uFragIdx,
> + cbLastFragmentSize,
> + uMACfragNum,
> + byFBOption));
> buf->time_stamp_off = vnt_time_stamp_off(pDevice, wCurrentRate);
> return buf->duration;
> }
> --
> 2.7.4
>
>
>
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#188): https://lists.elisa.tech/g/linux-safety/message/188
Mute This Topic: https://lists.elisa.tech/mt/78451464/5278000
Group Owner: linux-safety+owner@lists.elisa.tech
Unsubscribe: https://lists.elisa.tech/g/linux-safety/unsub [linux-safety@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2020-11-23 13:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 11:59 [linux-safety] [PATCH 1/2] staging: vt6655: Fix alignment in device_main.c Milan Lakhani
2020-11-23 11:59 ` [linux-safety] [PATCH 2/2] staging: vt6655: Correct wrappping in rxtx.c Milan Lakhani
2020-11-23 13:17 ` Lukas Bulwahn [this message]
2020-11-24 10:32 ` Milan Lakhani
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=CAKXUXMym-YfjQdDx7DcW8VHZH2bV5DbO6t0EgzmqD5hDe1AOZA@mail.gmail.com \
--to=lukas.bulwahn@gmail.com \
--cc=forest@alittletooquiet.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-safety@lists.elisa.tech \
--cc=milan.lakhani@codethink.co.uk \
/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).