public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frank Rowand <frowand.list@gmail.com>
To: Pantelis Antoniou <pantelis.antoniou@konsulko.com>
Cc: Rob Herring <robherring2@gmail.com>,
	Matt Porter <mporter@konsulko.com>,
	Koen Kooi <koen@dominion.thruhere.net>,
	Guenter Roeck <linux@roeck-us.net>, Marek Vasut <marex@denx.de>,
	Wolfram Sang <wsa@the-dreams.de>,
	Stephen Boyd <stephen.boyd@linaro.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-i2c@vger.kernel.org,
	Pantelis Antoniou <panto@antoniou-consulting.com>
Subject: Re: [RFC 3/3] dts: beaglebone: Portable connector BB_RELAY_4PORT definition
Date: Mon, 27 Jun 2016 10:56:13 -0700	[thread overview]
Message-ID: <577168BD.5030409@gmail.com> (raw)
In-Reply-To: <1464986273-12039-4-git-send-email-pantelis.antoniou@konsulko.com>

On 06/03/16 13:37, Pantelis Antoniou wrote:
> Example of a portable connector port for the BB_RELAY_4PORT cape
> 
> Signed-off-by: Pantelis Antoniou <pantelis.antoniou@konsulko.com>
> ---
>  arch/arm/boot/dts/am335x-bone-common.dtsi | 48 +++++++++++++++++++++++++++++++
>  1 file changed, 48 insertions(+)

Pantelis,

Can you provide a pointer to information about the cape?

Thanks,

Frank

  reply	other threads:[~2016-06-27 17:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-03 20:37 [RFC 0/3] Portable Device Tree Connector Pantelis Antoniou
2016-06-03 20:37 ` [RFC 1/3] of: Portable Device Tree connector Pantelis Antoniou
2016-06-03 20:37 ` [RFC 2/3] dts: Beaglebone portable connector definitions Pantelis Antoniou
2016-06-03 20:37 ` [RFC 3/3] dts: beaglebone: Portable connector BB_RELAY_4PORT definition Pantelis Antoniou
2016-06-27 17:56   ` Frank Rowand [this message]
2016-06-27 18:52     ` Pantelis Antoniou
2023-12-01 12:19 ` [RFC 0/3] Portable Device Tree Connector Kieran Bingham

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=577168BD.5030409@gmail.com \
    --to=frowand.list@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=koen@dominion.thruhere.net \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=marex@denx.de \
    --cc=mporter@konsulko.com \
    --cc=pantelis.antoniou@konsulko.com \
    --cc=panto@antoniou-consulting.com \
    --cc=robherring2@gmail.com \
    --cc=stephen.boyd@linaro.org \
    --cc=wsa@the-dreams.de \
    /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