From: Greg KH <gregkh@linuxfoundation.org>
To: Sean Cleator <seancleator@hotmail.co.uk>
Cc: David Matlack <matlackdavid@gmail.com>,
devel@driverdev.osuosl.org, Vincent Heuken <me@vincentheuken.com>,
linux-kernel@vger.kernel.org, Lior Dotan <liodot@gmail.com>,
Christopher Harrer <charrer@alacritech.com>,
Monam Agarwal <monamagarwal123@gmail.com>,
Joe Perches <joe@perches.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: [PATCH] Staging: slicoss: Fix long line issues in slicoss.c
Date: Sat, 17 Jan 2015 16:13:31 -0800 [thread overview]
Message-ID: <20150118001331.GA32461@kroah.com> (raw)
In-Reply-To: <BLU436-SMTP26EFE4C56ADB4FB217BA7EE97B0@phx.gbl>
On Wed, Dec 03, 2014 at 01:53:18PM +0000, Sean Cleator wrote:
> A patch to the slicoss.c file to fix some of the long line issues found by the
> checkpath.pl tool
>
> Signed-off-by: Sean Cleator <seancleator@hotmail.co.uk>
>
> ---
> drivers/staging/slicoss/slicoss.c | 39 ++++++++++++++++++++++++++-------------
> 1 file changed, 26 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/staging/slicoss/slicoss.c b/drivers/staging/slicoss/slicoss.c
> index 56ca3b6..4df4a7e 100644
> --- a/drivers/staging/slicoss/slicoss.c
> +++ b/drivers/staging/slicoss/slicoss.c
> @@ -498,12 +498,14 @@ static int slic_card_download(struct adapter *adapter)
> slic_reg32_write(&slic_regs->slic_wcs,
> baseaddress + codeaddr, FLUSH);
> /* Write out instruction to low addr */
> - slic_reg32_write(&slic_regs->slic_wcs, instruction, FLUSH);
> + slic_reg32_write(&slic_regs->slic_wcs,
> + instruction, FLUSH);
> instruction = *(u32 *)(fw->data + index);
> index += 4;
>
> /* Write out instruction to high addr */
> - slic_reg32_write(&slic_regs->slic_wcs, instruction, FLUSH);
> + slic_reg32_write(&slic_regs->slic_wcs,
> + instruction, FLUSH);
> instruction = *(u32 *)(fw->data + index);
> index += 4;
> }
> @@ -1533,14 +1535,18 @@ retry_rcvqfill:
> dev_err(dev, "%s: LOW 32bits PHYSICAL ADDRESS == 0\n",
> __func__);
> dev_err(dev, "skb[%p] PROBLEM\n", skb);
> - dev_err(dev, " skbdata[%p]\n", skb->data);
> + dev_err(dev, " skbdata[%p]\n",
> + skb->data);
> dev_err(dev, " skblen[%x]\n", skb->len);
> dev_err(dev, " paddr[%p]\n", paddr);
> dev_err(dev, " paddrl[%x]\n", paddrl);
> dev_err(dev, " paddrh[%x]\n", paddrh);
> - dev_err(dev, " rcvq->head[%p]\n", rcvq->head);
> - dev_err(dev, " rcvq->tail[%p]\n", rcvq->tail);
> - dev_err(dev, " rcvq->count[%x]\n", rcvq->count);
> + dev_err(dev, " rcvq->head[%p]\n",
> + rcvq->head);
> + dev_err(dev, " rcvq->tail[%p]\n",
> + rcvq->tail);
> + dev_err(dev, " rcvq->count[%x]\n",
> + rcvq->count);
> dev_err(dev, "SKIP THIS SKB!!!!!!!!\n");
> goto retry_rcvqfill;
> }
This change makes the code look worse, don't you think? Please don't do
that.
thanks,
greg k-h
next prev parent reply other threads:[~2015-01-18 0:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 13:53 [PATCH] Staging: slicoss: Fix long line issues in slicoss.c Sean Cleator
2015-01-18 0:13 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-12-02 23:45 Sean Cleator
2014-12-03 6:08 ` Sudip Mukherjee
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=20150118001331.GA32461@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=charrer@alacritech.com \
--cc=devel@driverdev.osuosl.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liodot@gmail.com \
--cc=matlackdavid@gmail.com \
--cc=me@vincentheuken.com \
--cc=monamagarwal123@gmail.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=seancleator@hotmail.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