All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] python-pigpio: new package
Date: Tue, 9 Oct 2018 15:40:53 +0200	[thread overview]
Message-ID: <20181009154053.2f01b0a1@windsurf> (raw)
In-Reply-To: <20180928180034.6543-2-grzegorz@blach.pl>

Hello,

On Fri, 28 Sep 2018 20:00:34 +0200, Grzegorz Blach wrote:
> Pigpio is a Python module for the Raspberry Pi
> which talks to the pigpio daemon to allow control
> of the general purpose input outputs (GPIO).
> 
> http://abyz.co.uk/rpi/pigpio/python.html
> 
> Signed-off-by: Grzegorz Blach <grzegorz@blach.pl>
> ---
>  DEVELOPERS                               |  1 +
>  package/Config.in                        |  1 +
>  package/python-pigpio/Config.in          |  8 ++++++++
>  package/python-pigpio/python-pigpio.hash |  3 +++
>  package/python-pigpio/python-pigpio.mk   | 13 +++++++++++++
>  5 files changed, 26 insertions(+)
>  create mode 100644 package/python-pigpio/Config.in
>  create mode 100644 package/python-pigpio/python-pigpio.hash
>  create mode 100644 package/python-pigpio/python-pigpio.mk

I've applied, with just a fix to use the proper SPDX license tag.

Could you ask the upstream project to add a license file to the
tarball ? It would be a nice addition.

Thanks a lot,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-10-09 13:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-28 18:00 [Buildroot] [PATCH 1/2] pigpio: new package Grzegorz Blach
2018-09-28 18:00 ` [Buildroot] [PATCH 2/2] python-pigpio: " Grzegorz Blach
2018-10-09 13:40   ` Thomas Petazzoni [this message]
2018-10-09 13:37 ` [Buildroot] [PATCH 1/2] pigpio: " Thomas Petazzoni

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=20181009154053.2f01b0a1@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 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.