From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/tpm2-tools: drop unused dbus / libglib2 dependencies
Date: Thu, 4 Apr 2019 22:54:22 +0200 [thread overview]
Message-ID: <20190404225422.11d35d02@windsurf> (raw)
In-Reply-To: <20190404190028.16680-1-peter@korsgaard.com>
On Thu, 4 Apr 2019 21:00:28 +0200
Peter Korsgaard <peter@korsgaard.com> wrote:
> tpm2-tools does not need dbus or libglib2, so remove them and the
> corresponding toolchain dependencies.
>
> The confusion may have come from the upstream travis configuration, which
> also builds tpm2-abrmd (which uses dbus+libglib2).
>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
> package/tpm2-tools/Config.in | 11 ++---------
> package/tpm2-tools/tpm2-tools.mk | 2 +-
> 2 files changed, 3 insertions(+), 10 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-04-04 20:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 19:00 [Buildroot] [PATCH] package/tpm2-tools: drop unused dbus / libglib2 dependencies Peter Korsgaard
2019-04-04 20:54 ` Thomas Petazzoni [this message]
2019-04-05 20:48 ` Peter Korsgaard
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=20190404225422.11d35d02@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox