All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Tero Marttila <tero.marttila@aalto.fi>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
	Luis de Bethencourt <luis@debethencourt.com>
Subject: Re: [PATCH] staging: octeon: Fix checkpatch line spacing warnings
Date: Sat, 17 Jan 2015 15:00:37 -0800	[thread overview]
Message-ID: <20150117230037.GA3781@kroah.com> (raw)
In-Reply-To: <1421080058-8871-1-git-send-email-tero.marttila@aalto.fi>

On Mon, Jan 12, 2015 at 06:27:38PM +0200, Tero Marttila wrote:
> Fix missing blank lines after declarations in octeon/ethernet-rx.c
> 
> Signed-off-by: Tero Marttila <tero.marttila@aalto.fi>
> ---
>  drivers/staging/octeon/ethernet-rx.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/staging/octeon/ethernet-rx.c b/drivers/staging/octeon/ethernet-rx.c
> index fcbe836..22667db 100644
> --- a/drivers/staging/octeon/ethernet-rx.c
> +++ b/drivers/staging/octeon/ethernet-rx.c
> @@ -109,6 +109,7 @@ static inline int cvm_oct_check_rcv_error(cvmx_wqe_t *work)
>  		int interface = cvmx_helper_get_interface_num(work->ipprt);
>  		int index = cvmx_helper_get_interface_index_num(work->ipprt);
>  		union cvmx_gmxx_rxx_frm_ctl gmxx_rxx_frm_ctl;
> +
>  		gmxx_rxx_frm_ctl.u64 =
>  		    cvmx_read_csr(CVMX_GMXX_RXX_FRM_CTL(index, interface));
>  		if (gmxx_rxx_frm_ctl.s.pre_chk == 0) {
> @@ -214,6 +215,7 @@ static int cvm_oct_napi_poll(struct napi_struct *napi, int budget)
>  		did_work_request = 0;
>  		if (work == NULL) {
>  			union cvmx_pow_wq_int wq_int;
> +
>  			wq_int.u64 = 0;
>  			wq_int.s.iq_dis = 1 << pow_receive_group;
>  			wq_int.s.wq_int = 1 << pow_receive_group;
> -- 
> 1.9.1

Someone else sent this before you did, sorry :(

      reply	other threads:[~2015-01-17 23:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-12 16:27 [PATCH] staging: octeon: Fix checkpatch line spacing warnings Tero Marttila
2015-01-17 23:00 ` 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=20150117230037.GA3781@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luis@debethencourt.com \
    --cc=tero.marttila@aalto.fi \
    /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.