From: Tony Lindgren <tony@atomide.com>
To: Robert Nelson <robertcnelson@gmail.com>
Cc: devicetree@vger.kernel.org, Drew Fustini <drew@beagleboard.org>,
Peter Robinson <pbrobinson@redhat.com>,
Jason Kridner <jkridner@beagleboard.org>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3] ARM: dts: Add am335x-pocketbeagle
Date: Tue, 1 May 2018 08:30:08 -0700 [thread overview]
Message-ID: <20180501153008.GD98604@atomide.com> (raw)
In-Reply-To: <20180417171404.13624-1-robertcnelson@gmail.com>
* Robert Nelson <robertcnelson@gmail.com> [180417 10:15]:
> PocketBeagle is an ultra-tiny-yet-complete open-source USB-key-fob computer.
>
> This board family can be indentified by the A335PBGL in the at24 eeprom:
> A2: [aa 55 33 ee 41 33 33 35 50 42 47 4c 30 30 41 32 |.U3.A335PBGL00A2|]
>
> http://beagleboard.org/pocket
> https://github.com/beagleboard/pocketbeagle
>
> Signed-off-by: Robert Nelson <robertcnelson@gmail.com>
> CC: Tony Lindgren <tony@atomide.com>
> CC: Jason Kridner <jkridner@beagleboard.org>
> CC: Drew Fustini <drew@beagleboard.org>
> CC: Peter Robinson <pbrobinson@redhat.com>
> ---
> Changes in v3:
> - Fix: Board eeprom in subject message. (accidently copied PocketBone)
> Changes in v2:
> - Use SPDX tags.
> - Use eeprom@50, remove repeated node and fix and remove '_' to fix node_name_chars_strict Warning
> - Fix: PocketBeagle Name in Subject (not PocketBeagle Blue)
> - Fix: leds remove '_' to fix node_name_chars_strict warning
> - Fix: node_name_chars_strict pinmux_*_pins label's.
Thanks applying into omap-for-v4.18/dt.
Tony
prev parent reply other threads:[~2018-05-01 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 17:14 [PATCH v3] ARM: dts: Add am335x-pocketbeagle Robert Nelson
2018-05-01 15:30 ` Tony Lindgren [this message]
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=20180501153008.GD98604@atomide.com \
--to=tony@atomide.com \
--cc=devicetree@vger.kernel.org \
--cc=drew@beagleboard.org \
--cc=jkridner@beagleboard.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=pbrobinson@redhat.com \
--cc=robertcnelson@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).