From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Harsha Sharma <harshasharmaiitr@gmail.com>
Cc: netfilter-devel@vger.kernel.org, outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH] nftables: make pointers in string arrays constant
Date: Fri, 6 Oct 2017 15:25:02 +0200 [thread overview]
Message-ID: <20171006132502.GA17724@salvia> (raw)
In-Reply-To: <20171005084647.22988-1-harshasharmaiitr@gmail.com>
On Thu, Oct 05, 2017 at 02:16:47PM +0530, Harsha Sharma wrote:
> static const char * array should probably be static const char *
> const array as per linux-kernel coding style
$ git am /tmp/nftables-make-pointers-in-string-arrays-constant.patch
Applying: nftables: make pointers in string arrays constant
error: patch failed: src/evaluate.c:33
error: src/evaluate.c: patch does not apply
It seems this patch doesn't apply cleanly.
Please, git pull --rebase on your tree and resend this patch.
Thanks.
prev parent reply other threads:[~2017-10-06 13:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 8:46 [PATCH] nftables: make pointers in string arrays constant Harsha Sharma
2017-10-06 13:25 ` Pablo Neira Ayuso [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=20171006132502.GA17724@salvia \
--to=pablo@netfilter.org \
--cc=harshasharmaiitr@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=outreachy-kernel@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).