From: Dengke Du <dengke.du@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH V2 0/1] ltp: upgrade to upstream latest commit on 20170804
Date: Fri, 4 Aug 2017 18:00:14 +0800 [thread overview]
Message-ID: <cover.1501840728.git.dengke.du@windriver.com> (raw)
The following changes since commit 9ed748a542b520c1cb763d981969233c0f5efd4e:
bitbake: daemonize: Always print any remaning UI events at exit (2017-08-03 11:14:13 +0100)
are available in the git repository at:
https://github.com/DengkeDu/openembedded-core.git dengke/ltp-upgrade-to-20170804
https://github.com//tree/dengke/ltp-upgrade-to-20170804
Dengke Du (1):
ltp: upgrade to upstream latest commit on 20170804
.../ltp/ltp/0001-dirtyc0w-Include-stdint.h.patch | 34 ------
...TH_MAX-undeclared-when-building-with-musl.patch | 31 -----
...faccessat-and-fchmodat-Fix-build-warnings.patch | 68 -----------
...d_key02-update-to-test-fix-for-nonempty-N.patch | 136 ---------------------
meta/recipes-extended/ltp/ltp_20170516.bb | 14 +--
5 files changed, 1 insertion(+), 282 deletions(-)
delete mode 100644 meta/recipes-extended/ltp/ltp/0001-dirtyc0w-Include-stdint.h.patch
delete mode 100644 meta/recipes-extended/ltp/ltp/0006-fix-PATH_MAX-undeclared-when-building-with-musl.patch
delete mode 100644 meta/recipes-extended/ltp/ltp/0037-faccessat-and-fchmodat-Fix-build-warnings.patch
delete mode 100644 meta/recipes-extended/ltp/ltp/0038-syscalls-add_key02-update-to-test-fix-for-nonempty-N.patch
--
2.7.4
next reply other threads:[~2017-08-04 10:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 10:00 Dengke Du [this message]
2017-08-04 10:00 ` [PATCH V2 1/1] ltp: upgrade to upstream latest commit on 20170804 Dengke Du
2017-08-09 20:47 ` Burton, Ross
2017-08-11 1:15 ` Dengke Du
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=cover.1501840728.git.dengke.du@windriver.com \
--to=dengke.du@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 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.