public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Michael Gunselmann <michael.gunselmann@studium.uni-erlangen.de>
Cc: devel@driverdev.osuosl.org, linux-kernel@i4.cs.fau.de,
	gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
	martin.hofmann@studium.uni-erlangen.de,
	forest@alittletooquiet.net
Subject: Re: [PATCH 2/7] vt6655: Fix most of checkpatch.pl errors in wroute
Date: Tue, 31 Dec 2013 14:12:25 +0300	[thread overview]
Message-ID: <20131231111225.GT28413@mwanda> (raw)
In-Reply-To: <1388415157-17615-3-git-send-email-michael.gunselmann@studium.uni-erlangen.de>

On Mon, Dec 30, 2013 at 03:52:32PM +0100, Michael Gunselmann wrote:
> wroute.h: Fixed all line-over-80-character errors. No errors remain.
> wroute.c: Fixed line-over-80-character errors, bracing errors
> 	  and C99-comments.
> 	  Three warnings remain, fixing them would deteriorate readability.
> 	  One warning on a memory barrier without comment in line 189
> 	  will be fixed in a later commit because it's purpose is not
> 	  yet known.
> 

Don't do the weird indenting.

> @@ -86,22 +88,25 @@ bool ROUTEbRelay(PSDevice pDevice, unsigned char *pbySkbData, unsigned int uData
>  
>  	pHeadTD->m_td1TD1.byTCR = (TCR_EDP | TCR_STP);
>  
> -	memcpy(pDevice->sTxEthHeader.abyDstAddr, (unsigned char *)pbySkbData, ETH_HLEN);
> +	memcpy(pDevice->sTxEthHeader.abyDstAddr,
> +	       (unsigned char *)pbySkbData, ETH_HLEN);
>  

It would be better to fix this like so:

	memcpy(pDevice->sTxEthHeader.abyDstAddr, pbySkbData, ETH_HLEN);

> -			}
> +			else
> +				pDevice->wCurrentRate =
> +					(unsigned short)pDevice->uConnectionRate;

Remove the silly cast here as well.

				pDevice->wCurrentRate = pDevice->uConnectionRate;

Both your patch and mine are still 81 characters long.

I don't get upset by lines over 80 characters...  Eventually we will fix
that.  Just leave it as-is, until we can clean it up from a human
perspective as well as from a checkpatch.pl robot perspective.

regards,
dan carpenter


  reply	other threads:[~2013-12-31 11:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-30 14:52 [PATCH 0/7] vt6655: Cleanup of checkpatch errors Michael Gunselmann
2013-12-30 14:52 ` [PATCH 1/7] vt6655: Remove unused macros in 80211hdr.h Michael Gunselmann
2013-12-31 16:55   ` Dan Carpenter
2013-12-30 14:52 ` [PATCH 2/7] vt6655: Fix most of checkpatch.pl errors in wroute Michael Gunselmann
2013-12-31 11:12   ` Dan Carpenter [this message]
2013-12-30 14:52 ` [PATCH 3/7] vt6655: Fixed most of the checkpatch warnings in wpactl Michael Gunselmann
2013-12-30 14:52 ` [PATCH 4/7] vt6655: Fixed most of the checkpatch warnings in wpa2 Michael Gunselmann
2013-12-31 16:52   ` Dan Carpenter
2013-12-30 14:52 ` [PATCH 5/7] vt6655: Fixed most of the checkpatch warnings in wpa Michael Gunselmann
2013-12-30 14:52 ` [PATCH 6/7] vt6655: Remove typedefs in 80211hdr.h Michael Gunselmann
2013-12-30 14:52 ` [PATCH 7/7] vt6655: Fixed most of the checkpatch warnings in wmgr Michael Gunselmann
2014-01-02 14:57   ` 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=20131231111225.GT28413@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=forest@alittletooquiet.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@i4.cs.fau.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.hofmann@studium.uni-erlangen.de \
    --cc=michael.gunselmann@studium.uni-erlangen.de \
    /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