From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Shivani Bhardwaj <shivanib134@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] configure: Fix logic for flex version check
Date: Fri, 17 Jun 2016 13:00:53 +0200 [thread overview]
Message-ID: <20160617110053.GA3372@salvia> (raw)
In-Reply-To: <1466114774-1831-1-git-send-email-shivanib134@gmail.com>
Hi Shivani,
On Fri, Jun 17, 2016 at 03:36:14AM +0530, Shivani Bhardwaj wrote:
> According to the previous logic of version check for flex, anything
> greater than 2.5.33 but within 2.5.x was acceptable. The issue was
> observed when a false warning generated for flex version 2.6.0.
> New logic works for basically everything greater than 2.5.33.
The patch doesn't say what tree this patch is intended for.
Anyway, this idiom has been copy and pasted from other netfilter
trees so it would be good to check if conntrack-tools, iptables and
nft suffer from this problem that you describe above.
Please, resubmit including prefix, eg. [PATCH iptables] configure: ...
and let me know, thanks.
prev parent reply other threads:[~2016-06-17 11:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 22:06 [PATCH] configure: Fix logic for flex version check Shivani Bhardwaj
2016-06-17 11:00 ` 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=20160617110053.GA3372@salvia \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=shivanib134@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 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).