public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: catalinnow@gmail.com
Cc: gregkh@linuxfoundation.org, aaro.koskinen@iki.fi,
	davem@davemloft.net, johannes.berg@intel.com,
	stephen@networkplumber.org, tklauser@distanz.ch,
	chuckleberryfinn@gmail.com, arnd@arndb.de,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: octeon: fix line over 80 characters
Date: Tue, 25 Jul 2017 17:13:46 +0300	[thread overview]
Message-ID: <20170725141346.2ncdfdz6uymecoc6@mwanda> (raw)
In-Reply-To: <1500987717-25307-1-git-send-email-catalinnow@gmail.com>

On Tue, Jul 25, 2017 at 04:01:57PM +0300, catalinnow@gmail.com wrote:
> From: John Smith <catalinnow@gmail.com>
> 
> ethernet-rx.c:
> 
> fix WARNING: line over 80 characters
> 
> Signed-off-by: John Smith <catalinnow@gmail.com>
> ---
>  drivers/staging/octeon/ethernet-rx.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/staging/octeon/ethernet-rx.c b/drivers/staging/octeon/ethernet-rx.c
> index 72baede..623c5e0 100644
> --- a/drivers/staging/octeon/ethernet-rx.c
> +++ b/drivers/staging/octeon/ethernet-rx.c
> @@ -323,7 +323,8 @@ static int cvm_oct_poll(struct oct_rx_group *rx_group, int budget)
>  						segment_size = len;
>  					/* Copy the data into the packet */
>  					skb_put_data(skb,
> -						     cvmx_phys_to_ptr(segment_ptr.s.addr),
> +						     cvmx_phys_to_ptr(
> +						     segment_ptr.s.addr),

The original looks better.

regards,
dan carpenter

      parent reply	other threads:[~2017-07-25 14:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-25 13:01 [PATCH] staging: octeon: fix line over 80 characters catalinnow
2017-07-25 13:30 ` Joe Perches
2017-07-25 14:13 ` Dan Carpenter [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=20170725141346.2ncdfdz6uymecoc6@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=aaro.koskinen@iki.fi \
    --cc=arnd@arndb.de \
    --cc=catalinnow@gmail.com \
    --cc=chuckleberryfinn@gmail.com \
    --cc=davem@davemloft.net \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=johannes.berg@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stephen@networkplumber.org \
    --cc=tklauser@distanz.ch \
    /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