From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] hidapi: new package
Date: Tue, 17 Nov 2015 22:04:11 +0100 [thread overview]
Message-ID: <20151117220411.349143fa@free-electrons.com> (raw)
In-Reply-To: <1447692852-21669-1-git-send-email-Vincent.Riera@imgtec.com>
Dear Vicente Olivert Riera,
On Mon, 16 Nov 2015 16:54:12 +0000, Vicente Olivert Riera wrote:
> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> ---
> package/Config.in | 1 +
> package/hidapi/Config.in | 20 ++++++++++++++++++++
> package/hidapi/hidapi.hash | 2 ++
> package/hidapi/hidapi.mk | 27 +++++++++++++++++++++++++++
> 4 files changed, 50 insertions(+), 0 deletions(-)
> create mode 100644 package/hidapi/Config.in
> create mode 100644 package/hidapi/hidapi.hash
> create mode 100644 package/hidapi/hidapi.mk
Applied to next, with a few changes:
[Thomas:
- use BR2_INIT_SYSTEMD instead of BR2_PACKAGE_SYSTEMD for the
libgudev handling. This is consistent with what we do in libmbim,
modem-manager and network-manager. Only udisks is diverging from
this by using BR2_PACKAGE_SYSTEMD.
- Fix the license info: it is GPLv3 *or* BSD-3c *or* the specific
HIDAPI license. Added LICENSE-orig.txt to LICENSE_FILES.]
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-11-17 21:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 16:54 [Buildroot] [PATCH] hidapi: new package Vicente Olivert Riera
2015-11-16 18:07 ` Baruch Siach
2015-11-17 10:11 ` Vicente Olivert Riera
2015-11-18 4:50 ` Baruch Siach
2015-11-18 8:22 ` Thomas Petazzoni
2015-11-18 8:45 ` Baruch Siach
2015-11-18 8:55 ` Thomas Petazzoni
2015-11-17 21:04 ` Thomas Petazzoni [this message]
2015-11-26 4:14 ` Alan Ott
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=20151117220411.349143fa@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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