devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Caleb Robey <c-robey@ti.com>
Cc: linux-patch-review@list.ti.com,
	"Jason Kridner" <jkridner@gmail.com>,
	"Lokesh Vutla" <lokeshvutla@ti.com>, "Jason Kridner" <jdk@ti.com>,
	"Faiz Abbas" <faiz_abbas@ti.com>,
	"Andreas Dannenberg" <dannenberg@ti.com>,
	"Jean-Jacques Hiblot" <jjhiblot@ti.com>,
	"Praneeth Bajjuri" <praneeth@ti.com>,
	"Andrew F . Davis" <afd@ti.com>,
	"Grygorii Strashko" <grygorii.strashko@ti.com>,
	"Robert Nelson" <robertcnelson@gmail.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Mark Rutland" <mark.rutland@arm.com>,
	"Benoît Cousson" <bcousson@baylibre.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-omap@vger.kernel.org
Subject: Re: [uL PATCH 1/2] ARM: dts: am5729: beaglebone-ai: adding device tree
Date: Thu, 14 Nov 2019 08:50:13 -0800	[thread overview]
Message-ID: <20191114165013.GP5610@atomide.com> (raw)
In-Reply-To: <20191113221345.4795-2-c-robey@ti.com>

* Caleb Robey <c-robey@ti.com> [191113 22:15]:
> From: Jason Kridner <jdk@ti.com>
> 
> BeagleBoard.org BeagleBone AI is an open source hardware single
> board computer based on the Texas Instruments AM5729 SoC featuring
> dual-core 1.5GHz Arm Cortex-A15 processor, dual-core C66 digital
> signal processor (DSP), quad-core embedded vision engine (EVE),
> Arm Cortex-M4 processors, dual programmable realtime unit
> industrial control subsystems and more. The board features 1GB
> DDR3L, USB3.0 Type-C, USB HS Type-A, microHDMI, 16GB eMMC flash,
> 1G Ethernet, 802.11ac 2/5GHz, Bluetooth, and BeagleBone expansion
> headers.
> 
> For more information, refer to:
> https://beaglebone.ai
> 
> This patch introduces the BeagleBone AI device tree.
> 
> Note that the device use the "ti,tpd12s016" component which is
> software compatible with "ti,tpd12s015". Thus we only use the
> latter driver.
> 
> Signed-off-by: Jason Kridner <jdk@ti.com>
> Cc: Robert Nelson <robertcnelson@gmail.com>
> Cc: Caleb Robey <c-robey@ti.com>

Hmm so this one has "From: Jason Kridner <jdk@ti.com>", but
seems like you may have updated it and are sending it out,
so it probably should also have your Signed-off-by.

Note that you can summarize your additions with something like:

Signed-off-by: Jason Kridner <jdk@ti.com>
[c-robey@ti.com: fixed up xyz against mainline kernel]
Signed-off-by: ...

Regards,

Tony

  reply	other threads:[~2019-11-14 16:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-13 22:13 [uL PATCH 0/2] Enable BeagleBone AI Caleb Robey
2019-11-13 22:13 ` [uL PATCH 1/2] ARM: dts: am5729: beaglebone-ai: adding device tree Caleb Robey
2019-11-14 16:50   ` Tony Lindgren [this message]
2019-11-13 22:13 ` [uL PATCH 2/2] ARM: dts: am5729: beaglebone-ai: dra7 reqs in dts Caleb Robey
2019-11-14 16:46   ` Tony Lindgren

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=20191114165013.GP5610@atomide.com \
    --to=tony@atomide.com \
    --cc=afd@ti.com \
    --cc=bcousson@baylibre.com \
    --cc=c-robey@ti.com \
    --cc=dannenberg@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=faiz_abbas@ti.com \
    --cc=grygorii.strashko@ti.com \
    --cc=jdk@ti.com \
    --cc=jjhiblot@ti.com \
    --cc=jkridner@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-patch-review@list.ti.com \
    --cc=lokeshvutla@ti.com \
    --cc=mark.rutland@arm.com \
    --cc=praneeth@ti.com \
    --cc=robertcnelson@gmail.com \
    --cc=robh+dt@kernel.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 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).