From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Robert Yang <liezhi.yang@windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/4] nfs-utils: 2.1.1 -> 2.3.1
Date: Thu, 15 Feb 2018 17:13:45 +0000 [thread overview]
Message-ID: <1518714825.24236.163.camel@linuxfoundation.org> (raw)
In-Reply-To: <fdad56afc0b04ea511507234935c6029303902b5.1517798422.git.liezhi.yang@windriver.com>
On Mon, 2018-02-05 at 10:41 +0800, Robert Yang wrote:
> * Remove 0001-configure-Allow-to-explicitly-disable-nfsidmap.patch,
> now the
> nfsidmap can't be disabled when nfsv4 is enabled, and nfsidmap
> requires
> keyutils, so we have to disable nfsv4 by default since keyutils is
> not
> available in oe-core, or we can add it oe-core.
>
> * Drop nfs-utils-1.2.3-sm-notify-res_init.patch and
> 0001-include-stdint.h-for-UINT16_MAX-definition.patch which are
> already in the
> source.
>
> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Fails on musl:
https://autobuilder.yocto.io/builders/nightly-musl/builds/782/steps/BuildImages/logs/stdio
Cheers,
Richard
next prev parent reply other threads:[~2018-02-15 17:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 2:41 [PATCH 0/4] Packages upgrade Robert Yang
2018-02-05 2:41 ` [PATCH 1/4] ccache: 3.3.4 -> 3.3.5 Robert Yang
2018-02-05 2:41 ` [PATCH 2/4] nfs-utils: 2.1.1 -> 2.3.1 Robert Yang
2018-02-15 17:13 ` Richard Purdie [this message]
2018-02-05 2:41 ` [PATCH 3/4] git: 2.15.0 -> 2.16.1 Robert Yang
2018-02-05 11:29 ` Peter Kjellerstedt
2018-02-06 4:46 ` Robert Yang
2018-02-05 2:41 ` [PATCH 4/4] time: 1.7 -> 1.8 Robert Yang
2018-02-15 18:30 ` Richard Purdie
2018-02-15 18:56 ` Andre McCurdy
2018-02-21 20:05 ` Burton, Ross
2018-02-22 2:31 ` Robert Yang
2018-02-22 2:31 ` Robert Yang
2018-02-05 3:03 ` ✗ patchtest: failure for Packages upgrade Patchwork
2018-02-05 4:25 ` Robert Yang
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=1518714825.24236.163.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=liezhi.yang@windriver.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