From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4] wiringpi: new package
Date: Fri, 3 Jun 2016 19:30:34 +0200 [thread overview]
Message-ID: <20160603193034.47625549@free-electrons.com> (raw)
In-Reply-To: <20160603192725.3a0beecd@gmx.net>
Hello,
On Fri, 3 Jun 2016 19:27:25 +0200, Peter Seiderer wrote:
> No idea what happened to wirinpi.com/drogon.net...
>
> But revision 78b5c323b74de782df58ee558c249e4e4fadd25f 'Bumped Version to 2.31'
> from https://github.com/WiringPi/WiringPi [1] has the same content
> as my local copy of wiringpi-2.31.tar.gz
OK. Can you send an updated version of the patch that uses this
alternate location?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-06-03 17:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 20:01 [Buildroot] [PATCH v4] wiringpi: new package Peter Seiderer
2016-06-03 13:26 ` Thomas Petazzoni
2016-06-03 17:27 ` Peter Seiderer
2016-06-03 17:30 ` Thomas Petazzoni [this message]
2016-06-03 18:14 ` Peter Seiderer
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=20160603193034.47625549@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