public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] libmnl: Update to version 1.0.5
Date: Sun, 10 Apr 2022 10:11:34 +0000	[thread overview]
Message-ID: <2d9d401a-f467-f5f9-b555-f410cfa361e1@ipfire.org> (raw)
In-Reply-To: <20220406130628.4999-1-adolf.belka@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1983 bytes --]

Reviewed-by: Peter Müller <peter.mueller(a)ipfire.org>

> - Update from 1.0.4 to 1.0.5
> - Update of rootfile not required
> - Changelog
>    Version 1.0.5 changes from git commits
> 	src: doc: Fix messed-up Netlink message batch diagram
> 	build: If doxygen is not available, be sure to report "doxygen: no" to ./conf...
> 	build: doc: get rid of the need for manual updating of Makefile
> 	build: doc: "make" builds & installs a full set of man pages
> 	doxygen: Fixed link to the git source tree on the website.
> 	include: add MNL_SOCKET_DUMP_SIZE definition
> 	doxygen: remove EXPORT_SYMBOL from the output
> 	nlmsg: Fix a missing doxygen section trailer
> 	src: fix doxygen function documentation
> 	examples: Add rtnl-addr-add.c
> 	examples: reduce LOCs during neigh attributes validation
> 	examples: fix print line format
> 	examples: fix neigh max attributes
> 	examples: add arp cache dump example
> 	libmnl: zero attribute padding
> 	examples: rtnl-addr-dump: fix typo
> 	callback: mark cb_ctl_array 'const' in mnl_cb_run2()
> 	examples: nfct-daemon: Fix test building on musl libc
> 
> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
> ---
>  lfs/libmnl | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/lfs/libmnl b/lfs/libmnl
> index 72273e3aa..9a96cdb7c 100644
> --- a/lfs/libmnl
> +++ b/lfs/libmnl
> @@ -24,7 +24,7 @@
>  
>  include Config
>  
> -VER        = 1.0.4
> +VER        = 1.0.5
>  
>  THISAPP    = libmnl-$(VER)
>  DL_FILE    = $(THISAPP).tar.bz2
> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
>  
>  $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>  
> -$(DL_FILE)_BLAKE2 = e24ae3e7a8bcfe35a04256c495bb3e9a5ec41b6bea9b7ffa0a8ebc82ce847921d4a44e5be3558239fee5008c10541a9ac3614d1a6b80d280b632a76da16be5e8
> +$(DL_FILE)_BLAKE2 = 760ec6f7eaf3f2c6be6edf848551e4c7d16ae7cbe49f9cde297f5df06174fb7f9f490118942225558f0a89dabe9a4901c1b3b23fa1203132e36b86e6332564d6
>  
>  install : $(TARGET)
>  

      reply	other threads:[~2022-04-10 10:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06 13:06 Adolf Belka
2022-04-10 10:11 ` Peter Müller [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=2d9d401a-f467-f5f9-b555-f410cfa361e1@ipfire.org \
    --to=peter.mueller@ipfire.org \
    --cc=development@lists.ipfire.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