From: Phil Sutter <phil@nwl.cc>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: [arptables PATCH 0/3] Some minor fixes
Date: Thu, 21 Nov 2019 12:15:56 +0100 [thread overview]
Message-ID: <20191121111559.27066-1-phil@nwl.cc> (raw)
These are some patches I found while cleaning up the attic. They add a
gitignore file, fix for a compiler warning and simplify code in libarptc
a bit.
Phil Sutter (3):
Add .gitignore
Eliminate compiler warning about size passed to strncmp()
libarptc: Simplify alloc_handle by using calloc()
.gitignore | 4 ++++
arptables.c | 3 +--
libarptc/libarptc_incl.c | 11 +++--------
3 files changed, 8 insertions(+), 10 deletions(-)
create mode 100644 .gitignore
--
2.24.0
next reply other threads:[~2019-11-21 11:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 11:15 Phil Sutter [this message]
2019-11-21 11:15 ` [arptables PATCH 1/3] Add .gitignore Phil Sutter
2019-11-21 13:45 ` Pablo Neira Ayuso
2019-11-21 11:15 ` [arptables PATCH 2/3] Eliminate compiler warning about size passed to strncmp() Phil Sutter
2019-11-21 13:45 ` Pablo Neira Ayuso
2019-11-21 11:15 ` [arptables PATCH 3/3] libarptc: Simplify alloc_handle by using calloc() Phil Sutter
2019-11-21 13:46 ` Pablo Neira Ayuso
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=20191121111559.27066-1-phil@nwl.cc \
--to=phil@nwl.cc \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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 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).