From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-networking][PATCH v3] phytool: Add recipe
Date: Fri, 7 Oct 2016 08:10:56 +0200 [thread overview]
Message-ID: <nt7e9d$9p0$2@blaine.gmane.org> (raw)
In-Reply-To: <1475733541-3401-1-git-send-email-mike.looijmans@topic.nl>
Op 06-10-16 om 07:59 schreef Mike Looijmans:
> A nice tool to directly read, write and interpret ethernet PHY data.
> Very useful when debugging PHY or MDIO problems, which ethtool does
> not do.
>
> Signed-off-by: Mike Looijmans <mike.looijmans@topic.nl>
> ---
> v3: Add SRCPV to PV
> Indent using spaces instead of tab
> v2: Fix LICENSE filename and checksum
> Honor LDFLAGS value (patch accepted upstream)
> meta-networking/recipes-support/phytool/phytool.bb | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
> create mode 100644 meta-networking/recipes-support/phytool/phytool.bb
>
> diff --git a/meta-networking/recipes-support/phytool/phytool.bb b/meta-networking/recipes-support/phytool/phytool.bb
> new file mode 100644
> index 0000000..e4391df
> --- /dev/null
> +++ b/meta-networking/recipes-support/phytool/phytool.bb
> @@ -0,0 +1,14 @@
> +SUMMARY = "PHY interface tool for Linux"
> +LICENSE = "GPLv2"
> +LIC_FILES_CHKSUM = "file://LICENSE;md5=39bba7d2cf0ba1036f2a6e2be52fe3f0"
> +
> +PV = "1.0.1+git${SRCPV}"
> +SRCREV = "3149bfdb4f513e2f0da0a7d0bc5d0873578696f2"
> +SRC_URI = "git://github.com/wkz/phytool.git"
> +
> +S = "${WORKDIR}/git"
> +
> +do_install() {
> + install -d ${D}${prefix}/bin
${D}${bindir}
> + oe_runmake 'DESTDIR=${D}' 'PREFIX=${prefix}' install
> +}
>
next prev parent reply other threads:[~2016-10-07 6:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 5:59 [meta-networking][PATCH v3] phytool: Add recipe Mike Looijmans
2016-10-07 6:10 ` Koen Kooi [this message]
2016-10-07 6:23 ` Mike Looijmans
2016-10-07 6:31 ` [meta-networking][PATCH v4] " Mike Looijmans
2016-10-07 6:36 ` [meta-networking][PATCH v5] " Mike Looijmans
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='nt7e9d$9p0$2@blaine.gmane.org' \
--to=koen@dominion.thruhere.net \
--cc=openembedded-devel@lists.openembedded.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 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.