All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zoltan Kiss <zoltan.kiss@citrix.com>
To: Joe Perches <joe@perches.com>, Andy Whitcroft <apw@canonical.com>
Cc: David Miller <davem@davemloft.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: checkpatch minor issue
Date: Wed, 9 Jul 2014 16:00:49 +0100	[thread overview]
Message-ID: <53BD5921.4050405@citrix.com> (raw)
In-Reply-To: <20140708.112838.2087453949565741801.davem@davemloft.net>

Hi,

In one of my posted patch David spotted an indentation error, I thought 
these trivial mistakes are catched by checkpatch. Maybe it shouldn't, 
but otherwise you should check this issue, see it in the mail below.

Regards,

Zoli

-------- Original Message --------
Subject: Re: [PATCH net-next 1/3 v4] pktgen: Fill the payload optionally 
with a pattern
Date: Tue, 8 Jul 2014 11:28:38 -0700
From: David Miller <davem@davemloft.net>
To: <zoltan.kiss@citrix.com>
CC: <steffen.klassert@secunet.com>, <minipli@googlemail.com>, 
<dborkman@redhat.com>, <tgraf@suug.ch>, <joe@perches.com>, 
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>, 
<xen-devel@lists.xenproject.org>

From: Zoltan Kiss <zoltan.kiss@citrix.com>
Date: Wed, 2 Jul 2014 20:54:13 +0100

> @@ -1129,11 +1133,13 @@ static ssize_t pktgen_if_write(struct file *file,
>  		i += len;
>
>  		if (node_possible(value)) {
> +			int j;
>  			pkt_dev->node = value;
>  			sprintf(pg_result, "OK: node=%d", pkt_dev->node);
> -			if (pkt_dev->page) {
> -				put_page(pkt_dev->page);
> -				pkt_dev->page = NULL;
> +			for (j = 0; j < MAX_SKB_FRAGS; ++j)
> +				if (pkt_dev->pages[j]) {
> +					put_page(pkt_dev->pages[j]);
> +					pkt_dev->pages[j] = NULL;
>  			}
>  		}

I'm scratching my head with the bracing created here, and it's because
the indentation is wrong:

	for () /* <-- no openning curly brace */
		if () {
			x;
			y;
	} /* <-- thus, wrong indentation */

Please resubmit this series with this fixed and #3 adjusted as per the
feedback you've received.

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html



  parent reply	other threads:[~2014-07-09 15:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-02 19:54 [PATCH net-next v2 0/3] pktgen: Upstreaming features useful for xen-netback/front testing Zoltan Kiss
2014-07-02 19:54 ` [PATCH net-next 1/3 v4] pktgen: Fill the payload optionally with a pattern Zoltan Kiss
2014-07-08 18:28   ` David Miller
2014-07-08 18:28   ` David Miller
2014-07-09 14:51     ` Zoltan Kiss
2014-07-09 14:51     ` Zoltan Kiss
2014-07-09 15:00     ` Zoltan Kiss [this message]
2014-07-09 18:50       ` checkpatch minor issue Joe Perches
2014-07-02 19:54 ` [PATCH net-next 1/3 v4] pktgen: Fill the payload optionally with a pattern Zoltan Kiss
2014-07-02 19:54 ` [PATCH net-next v2 2/3] pktgen: Allow setting frag sizes individually Zoltan Kiss
2014-07-02 19:54 ` Zoltan Kiss
2014-07-02 19:54 ` [PATCH net-next v2 3/3 RFC] pktgen: Allow sending TCP packets Zoltan Kiss
2014-07-02 19:54 ` Zoltan Kiss
2014-07-03  6:49   ` Eric Dumazet
2014-07-03  6:49   ` Eric Dumazet

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=53BD5921.4050405@citrix.com \
    --to=zoltan.kiss@citrix.com \
    --cc=apw@canonical.com \
    --cc=davem@davemloft.net \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    /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.