From: <kai.kang@windriver.com>
To: <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH V2 0/2] Remove allarch from recipes which rdeps TUNE_PKGARCH packages
Date: Fri, 3 Aug 2018 09:49:45 +0800 [thread overview]
Message-ID: <20180803014947.23598-1-kai.kang@windriver.com> (raw)
From: Kai Kang <kai.kang@windriver.com>
V2:
* rebase on Ross's patch 'ca-certificates: upgrade 20170717 -> 20180409'
Kai Kang (2):
remove allarch from recipes which rdepends on TUNE_PKGARCH packages
layer.conf: update SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS
meta/conf/layer.conf | 7 -------
meta/recipes-connectivity/ppp-dialin/ppp-dialin_0.1.bb | 2 +-
meta/recipes-connectivity/resolvconf/resolvconf_1.79.bb | 2 --
meta/recipes-core/initrdscripts/initramfs-framework_1.0.bb | 2 --
.../initrdscripts/initramfs-module-setup-live_1.0.bb | 2 --
.../docbook-xml/docbook-xsl-stylesheets_1.79.1.bb | 1 -
meta/recipes-graphics/wayland/weston-init.bb | 2 +-
meta/recipes-graphics/xorg-font/font-alias_1.0.3.bb | 2 --
meta/recipes-graphics/xorg-font/xorg-minimal-fonts.bb | 2 +-
.../ca-certificates/ca-certificates_20180409.bb | 2 --
10 files changed, 3 insertions(+), 21 deletions(-)
--
2.17.1
next reply other threads:[~2018-08-03 2:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 1:49 kai.kang [this message]
2018-08-03 1:49 ` [PATCH 1/2] remove allarch from recipes which rdepends on TUNE_PKGARCH packages kai.kang
2018-08-03 21:28 ` richard.purdie
2018-08-06 14:51 ` Mark Hatle
2018-08-07 9:37 ` Kang Kai
2018-08-07 10:44 ` richard.purdie
2018-08-07 14:56 ` Richard Purdie
2018-08-07 17:07 ` Mark Hatle
2018-08-03 1:49 ` [PATCH 2/2] layer.conf: update SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS kai.kang
2018-08-03 2:32 ` ✗ patchtest: failure for Remove allarch from recipes which rdeps TUNE_PKGARCH packages (rev2) Patchwork
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=20180803014947.23598-1-kai.kang@windriver.com \
--to=kai.kang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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