From: <kai.kang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/2] Fix build errors for x32
Date: Thu, 13 Dec 2018 09:14:09 -0500 [thread overview]
Message-ID: <cover.1544710323.git.kai.kang@windriver.com> (raw)
From: Kai Kang <kai.kang@windriver.com>
The following changes since commit e235a9e18bad4758650c11cd98133de695b72bd1:
bitbake: bitbake-user-manual: Added "usehead" parameter. (2018-12-10 20:32:05 +0000)
are available in the Git repository at:
git://git.pokylinux.org/poky-contrib kangkai/systemd-req
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=kangkai/systemd-req
Kai Kang (2):
systemd: fix compile error for x32
lttng-tools: fix compile error for x32
...hanges-type-of-drift_freq-to-int64_t.patch | 49 +++++++++++++++++++
meta/recipes-core/systemd/systemd_239.bb | 1 +
.../lttng/lttng-tools/x32.patch | 28 +++++++++--
3 files changed, 74 insertions(+), 4 deletions(-)
create mode 100644 meta/recipes-core/systemd/systemd/0001-timesync-changes-type-of-drift_freq-to-int64_t.patch
--
2.19.0.rc2
next reply other threads:[~2018-12-13 14:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 14:14 kai.kang [this message]
2018-12-13 14:14 ` [PATCH 1/2] systemd: fix compile error for x32 kai.kang
2018-12-13 14:14 ` [PATCH 2/2] lttng-tools: " kai.kang
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.1544710323.git.kai.kang@windriver.com \
--to=kai.kang@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.