All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] package/libnfs: bump to version 3.0.0
Date: Thu, 29 Nov 2018 22:38:00 +0100	[thread overview]
Message-ID: <20181129223800.239c22d3@windsurf> (raw)
In-Reply-To: <20181105171141.3814-1-joerg.krause@embedded.rocks>

Hello,

On Mon,  5 Nov 2018 18:11:41 +0100, J?rg Krause wrote:
> Also add an patch from upstream to fix building libnfs with the musl C
> library. This issue was introduced upstream between version 2.0.0 and
> version 3.0.0.
> 
> Note, that upstreams commit message says it fixes a warning. However, as
> musl is more strictly regarding missing headers it actually fixes the
> build with musl.
> 
> Furthermore, the COPYING license file was changed in the way that it now
> includes a clarification about the .x files being distributed under the
> simplified BSD license. We already note in LIBNFS_LICENSE that the .x
> files are BSD-2-Clause. So, updating the hash for this license file is
> enough.
> 
> Signed-off-by: J?rg Krause <joerg.krause@embedded.rocks>
> ---
> v2 -> v3:
>  - improve commit log regardings updating the hash of COPYING (Thomas)
> v1 -> v2:
>  - fix hash of license file COPYING
> ---
>  ...-libnfs.c-include-time.h-in-libnfs.c.patch | 35 +++++++++++++++++++
>  package/libnfs/libnfs.hash                    |  4 +--
>  package/libnfs/libnfs.mk                      |  2 +-
>  3 files changed, 38 insertions(+), 3 deletions(-)
>  create mode 100644 package/libnfs/0002-libnfs.c-include-time.h-in-libnfs.c.patch

Applied to next, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2018-11-29 21:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-05 17:11 [Buildroot] [PATCH v3] package/libnfs: bump to version 3.0.0 Jörg Krause
2018-11-29 21:38 ` Thomas Petazzoni [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=20181129223800.239c22d3@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.