From: Julia Lawall <julia.lawall@inria.fr>
To: Deepak R Varma <mh12gx2825@gmail.com>
Cc: outreachy-kernel@googlegroups.com,
Forest Bond <forest@alittletooquiet.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [Outreachy kernel] [PATCH] staging: vt6655: rearrange lines exceeding 100 columns
Date: Wed, 14 Oct 2020 18:01:39 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2010141801041.2687@hadrien> (raw)
In-Reply-To: <20201014154121.GA23584@ubuntu204>
On Wed, 14 Oct 2020, Deepak R Varma wrote:
> Rearrange lines that are longer than 100 columns width. Issue reported
> by chckpatch script.
>
> Signed-off-by: Deepak R Varma <mh12gx2825@gmail.com>
>
> ---
>
> drivers/staging/vt6655/device_main.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/vt6655/device_main.c b/drivers/staging/vt6655/device_main.c
> index 09ab6d6f2429..4fc90b111f9d 100644
> --- a/drivers/staging/vt6655/device_main.c
> +++ b/drivers/staging/vt6655/device_main.c
> @@ -461,7 +461,10 @@ static bool device_init_rings(struct vnt_private *priv)
> priv->opts.rx_descs0 * sizeof(struct vnt_rx_desc);
>
> priv->tx0_bufs = dma_alloc_coherent(&priv->pcid->dev,
> - priv->opts.tx_descs[0] * PKT_BUF_SZ + priv->opts.tx_descs[1] * PKT_BUF_SZ + CB_BEACON_BUF_SIZE + CB_MAX_BUF_SIZE,
> + priv->opts.tx_descs[0] * PKT_BUF_SZ +
> + priv->opts.tx_descs[1] * PKT_BUF_SZ +
> + CB_BEACON_BUF_SIZE +
> + CB_MAX_BUF_SIZE,
> &priv->tx_bufs_dma0, GFP_ATOMIC);
> if (!priv->tx0_bufs) {
> dev_err(&priv->pcid->dev, "allocate buf dma memory failed\n");
> @@ -1077,7 +1080,8 @@ static void vnt_interrupt_process(struct vnt_private *priv)
> priv->op_mode == NL80211_IFTYPE_ADHOC) &&
> priv->vif->bss_conf.enable_beacon) {
> MACvOneShotTimer1MicroSec(priv,
> - (priv->vif->bss_conf.beacon_int - MAKE_BEACON_RESERVED) << 10);
> + (priv->vif->bss_conf.beacon_int -
> + MAKE_BEACON_RESERVED) << 10);
Maybe it would make more sense to shorten the function name?
Also the {} are not needed.
julia
> }
>
> /* TODO: adhoc PS mode */
> --
> 2.25.1
>
> --
> You received this message because you are subscribed to the Google Groups "outreachy-kernel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to outreachy-kernel+unsubscribe@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/outreachy-kernel/20201014154121.GA23584%40ubuntu204.
>
next prev parent reply other threads:[~2020-10-14 16:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 15:41 [PATCH] staging: vt6655: rearrange lines exceeding 100 columns Deepak R Varma
2020-10-14 16:01 ` Julia Lawall [this message]
2020-10-14 16:38 ` [Outreachy kernel] " Deepak R Varma
2020-10-14 16:46 ` Julia Lawall
2020-10-14 17:09 ` Deepak R Varma
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=alpine.DEB.2.22.394.2010141801041.2687@hadrien \
--to=julia.lawall@inria.fr \
--cc=forest@alittletooquiet.net \
--cc=gregkh@linuxfoundation.org \
--cc=mh12gx2825@gmail.com \
--cc=outreachy-kernel@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.