From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Lungash <denizlungash@gmail.com>
Cc: Manish Chopra <manishc@marvell.com>,
GR-Linux-NIC-Dev@marvell.com, Coiby Xu <coiby.xu@gmail.com>,
netdev@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org, outreachy@lists.linux.dev
Subject: Re: [PATCH] staging: qlge: Fix line wrapping
Date: Fri, 22 Apr 2022 14:11:31 +0200 [thread overview]
Message-ID: <YmKbc9Ib9vXgDnBg@kroah.com> (raw)
In-Reply-To: <YmJseHLyoAJWOGpc@kali-h6>
On Fri, Apr 22, 2022 at 11:51:04AM +0300, Lungash wrote:
> This patch fixes line wrapping following kernel coding style.
>
> Task on TODO list
>
> * fix weird line wrapping (all over, ex. the ql_set_routing_reg() calls in
> qlge_set_multicast_list()).
>
> Signed-off-by: Lungash <denzlungash@gmail.com>
We need a "full" name here, whatever you sign legal documents with.
> ---
> drivers/staging/qlge/qlge_main.c | 235 ++++++++++++++-----------------
> 1 file changed, 107 insertions(+), 128 deletions(-)
>
> diff --git a/drivers/staging/qlge/qlge_main.c b/drivers/staging/qlge/qlge_main.c
> index 113a3efd12e9..309db00e0b22 100644
> --- a/drivers/staging/qlge/qlge_main.c
> +++ b/drivers/staging/qlge/qlge_main.c
> @@ -499,77 +499,57 @@ static int qlge_set_routing_reg(struct qlge_adapter *qdev, u32 index, u32 mask,
>
> switch (mask) {
> case RT_IDX_CAM_HIT:
> - {
> - value = RT_IDX_DST_CAM_Q | /* dest */
> - RT_IDX_TYPE_NICQ | /* type */
> - (RT_IDX_CAM_HIT_SLOT << RT_IDX_IDX_SHIFT);/* index */
> - break;
> - }
> + value = RT_IDX_DST_CAM_Q | /* dest */
> + RT_IDX_TYPE_NICQ | /* type */
> + (RT_IDX_CAM_HIT_SLOT << RT_IDX_IDX_SHIFT);/* index */
> + break;
The original was fine, but yes, the {} can be removed, but that does not
have to do with the TODO item here. Please only do one type of fixup at
a time.
>
> -static int qlge_validate_flash(struct qlge_adapter *qdev, u32 size, const char *str)
> +static int qlge_validate_flash(struct qlge_adapter *qdev, u32 size,
> + const char *str)
You just made this look worse, why?
> -static int qlge_read_flash_word(struct qlge_adapter *qdev, int offset, __le32 *data)
> +static int qlge_read_flash_word(struct qlge_adapter *qdev, int offset,
> + __le32 *data)
Same here, why change the original?
> @@ -2952,8 +2936,8 @@ static int qlge_start_rx_ring(struct qlge_adapter *qdev, struct rx_ring *rx_ring
> (rx_ring->cq_id * RX_RING_SHADOW_SPACE);
> u64 shadow_reg_dma = qdev->rx_ring_shadow_reg_dma +
> (rx_ring->cq_id * RX_RING_SHADOW_SPACE);
> - void __iomem *doorbell_area =
> - qdev->doorbell_area + (DB_PAGE_SIZE * (128 + rx_ring->cq_id));
> + void __iomem *doorbell_area = qdev->doorbell_area +
> + (DB_PAGE_SIZE * (128 + rx_ring->cq_id));
This does not look better, why not put it all on one line?
thanks,
greg k-h
prev parent reply other threads:[~2022-04-22 12:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 8:51 [PATCH] staging: qlge: Fix line wrapping Lungash
2022-04-22 12:11 ` Greg Kroah-Hartman [this message]
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=YmKbc9Ib9vXgDnBg@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=GR-Linux-NIC-Dev@marvell.com \
--cc=coiby.xu@gmail.com \
--cc=denizlungash@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=manishc@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=outreachy@lists.linux.dev \
/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).