From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Nicholas Krause <xerofoify@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, ast@plumgrid.com,
stephen@networkplumber.org, fabf@skynet.be, joe@perches.com,
sd@queasysnail.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, brouer@redhat.com
Subject: Re: [PATCHv3] pktgen: Convert return type of process_ipsec to bool
Date: Thu, 28 May 2015 12:11:02 +0200 [thread overview]
Message-ID: <20150528121102.566576af@redhat.com> (raw)
In-Reply-To: <1432786265-31021-1-git-send-email-xerofoify@gmail.com>
On Thu, 28 May 2015 00:11:05 -0400
Nicholas Krause <xerofoify@gmail.com> wrote:
> This converts the function, process_ipsec to the
> return type of bool due to only returning either
> one or zero.
>
> Signed-off-by: Nicholas Krause <xerofoify@gmail.com>
> ---
> v3
> Move the v2 changes below the sign off line for this patch.
> v2
> Change incorrect patch subject and make commit message
> clearer
> net/core/pktgen.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/net/core/pktgen.c b/net/core/pktgen.c
> index 508155b..33bdb76 100644
> --- a/net/core/pktgen.c
> +++ b/net/core/pktgen.c
> @@ -2587,7 +2587,7 @@ static void free_SAs(struct pktgen_dev *pkt_dev)
> }
> }
>
> -static int process_ipsec(struct pktgen_dev *pkt_dev,
> +static bool process_ipsec(struct pktgen_dev *pkt_dev,
> struct sk_buff *skb, __be16 protocol)
When doing this change, could you please align the above line to the
open parenthesis of process_ipsec (even-though it was also misaligned
before).
scripts/checkpatch.pl will tell you:
CHECK: Alignment should match open parenthesis
Did anyone tell you that kernel developers nitpick? ;-)
And usually you don't need to Cc the "main" Linux Kernel Mailing List
(linux-kernel@vger.kernel.org) with a trivial patch like this. Sending
it to the network developers should be enough (netdev@vger.kernel.org).
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Sr. Network Kernel Developer at Red Hat
Author of http://www.iptv-analyzer.org
LinkedIn: http://www.linkedin.com/in/brouer
parent reply other threads:[~2015-05-28 10:11 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1432786265-31021-1-git-send-email-xerofoify@gmail.com>]
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=20150528121102.566576af@redhat.com \
--to=brouer@redhat.com \
--cc=ast@plumgrid.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fabf@skynet.be \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sd@queasysnail.net \
--cc=stephen@networkplumber.org \
--cc=xerofoify@gmail.com \
/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.