From: Saul Wold <sgw@linux.intel.com>
To: Cristian Iorga <cristian.iorga@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] iptables: upgrade to 1.4.18
Date: Wed, 01 May 2013 11:20:39 -0700 [thread overview]
Message-ID: <51815CF7.4080605@linux.intel.com> (raw)
In-Reply-To: <1367317863-10350-1-git-send-email-cristian.iorga@intel.com>
On 04/30/2013 03:31 AM, Cristian Iorga wrote:
> fix-link-failure-ip6t-NETMAP.patch removed;
> already included in upstream.
>
You do not seem to have removed the patch file itself.
Sau!
> Signed-off-by: Cristian Iorga <cristian.iorga@intel.com>
> ---
> .../iptables/{iptables_1.4.17.bb => iptables_1.4.18.bb} | 8 +++-----
> 1 file changed, 3 insertions(+), 5 deletions(-)
> rename meta/recipes-extended/iptables/{iptables_1.4.17.bb => iptables_1.4.18.bb} (90%)
>
> diff --git a/meta/recipes-extended/iptables/iptables_1.4.17.bb b/meta/recipes-extended/iptables/iptables_1.4.18.bb
> similarity index 90%
> rename from meta/recipes-extended/iptables/iptables_1.4.17.bb
> rename to meta/recipes-extended/iptables/iptables_1.4.18.bb
> index aa932ce..bb8718f 100644
> --- a/meta/recipes-extended/iptables/iptables_1.4.17.bb
> +++ b/meta/recipes-extended/iptables/iptables_1.4.18.bb
> @@ -7,8 +7,6 @@ LICENSE = "GPLv2+"
> LIC_FILES_CHKSUM = "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263\
> file://iptables/iptables.c;beginline=13;endline=25;md5=c5cffd09974558cf27d0f763df2a12dc"
>
> -PR = "r1"
> -
> RRECOMMENDS_${PN} = "kernel-module-x-tables \
> kernel-module-ip-tables \
> kernel-module-iptable-filter \
> @@ -23,12 +21,12 @@ FILES_${PN}-dbg =+ "${libdir}/xtables/.debug"
>
> SRC_URI = "http://netfilter.org/projects/iptables/files/iptables-${PV}.tar.bz2 \
> file://types.h-add-defines-that-are-required-for-if_packet.patch \
> - file://fix-link-failure-ip6t-NETMAP.patch \
> file://fix-iptables-extensions-build-error.patch \
> file://0001-configure-Add-option-to-enable-disable-libnfnetlink.patch \
> "
> -SRC_URI[md5sum] = "c3fb2ffd5b39d0d54b06ccc4c8660116"
> -SRC_URI[sha256sum] = "51e7a769469383b6ad308a6a19cdd2bd813cf4593e21a156a543a1cd70554925"
> +
> +SRC_URI[md5sum] = "a819199d5ec013b82da13a8ffbba857e"
> +SRC_URI[sha256sum] = "14a99fb8b0ca22027a9ac6eb72fa32c834ceb3073820e0ba79bf251c6a7bcf3c"
>
> inherit autotools
>
>
next prev parent reply other threads:[~2013-05-01 18:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 10:31 [PATCH] iptables: upgrade to 1.4.18 Cristian Iorga
2013-05-01 18:20 ` Saul Wold [this message]
2013-05-07 8:01 ` Iorga, Cristian
-- strict thread matches above, loose matches on Subject: below --
2013-03-14 17:20 Cristian Iorga
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=51815CF7.4080605@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=cristian.iorga@intel.com \
--cc=openembedded-core@lists.openembedded.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