From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] package/libnftnl: bump to version 1.1.3
Date: Thu, 04 Jul 2019 06:55:31 +0300 [thread overview]
Message-ID: <87o92amp1o.fsf@tarshish> (raw)
In-Reply-To: <bac5f180-a5b8-5af6-d512-25bee2fce460@mind.be>
Hi Arnout,
On Thu, Jul 04 2019, Arnout Vandecappelle wrote:
> On 01/07/2019 14:12, Baruch Siach wrote:
>> Rebase patch #1.
>>
>> Cc: Yegor Yefremov <yegorslists@googlemail.com>
>> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
>
> Series applied to master, thanks.
>
>
>> ...libnftnl_xfree-to-avoid-symbol-namin.patch | 118 ++++++++++--------
>
> Could you check if this patch is still relevant? Originally, xfree was defined
> as a function so it made sense. However, in 1.0.3 it became a define so it
> shouldn't be needed anymore...
Right. Upstream commit 244d60de2f1 ("utils: define xfree() as macro") in
version 1.0.3 changed that following Thomas' bug report.
I'll send a patch.
> Also, is path 2 upstreamable?
I'll try.
Thanks,
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
prev parent reply other threads:[~2019-07-04 3:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 12:12 [Buildroot] [PATCH 1/3] package/libnftnl: bump to version 1.1.3 Baruch Siach
2019-07-01 12:12 ` [Buildroot] [PATCH 2/3] package/iptables: bump to version 1.8.3 Baruch Siach
2019-07-01 12:12 ` [Buildroot] [PATCH 3/3] package/ipset: bump to version 7.2 Baruch Siach
2019-07-03 22:02 ` [Buildroot] [PATCH 1/3] package/libnftnl: bump to version 1.1.3 Arnout Vandecappelle
2019-07-04 3:55 ` Baruch Siach [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=87o92amp1o.fsf@tarshish \
--to=baruch@tkos.co.il \
--cc=buildroot@busybox.net \
/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