From: Tony Lindgren <tony@atomide.com>
To: Caleb Robey <c-robey@ti.com>
Cc: linux-omap@vger.kernel.org, "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>,
"Tom Rini" <trini@konsulko.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
Subject: Re: [PATCH 1/2] ARM: dts: am5729: beaglebone-ai: dra7 reqs in dts
Date: Thu, 14 Nov 2019 09:47:05 -0800 [thread overview]
Message-ID: <20191114174705.GV5610@atomide.com> (raw)
In-Reply-To: <20191114170933.12623-2-c-robey@ti.com>
* Caleb Robey <c-robey@ti.com> [191114 17:11]:
Hmm I think this one is still missing
From: Jason Kridner <jdk@ti.com>
If this too is Jason's patch? This happens if you apply a patch
manually instead of applying an email with git am.
You might be able to just change the From: line with
git commit --amend.
Regards,
Tony
next prev parent reply other threads:[~2019-11-14 17:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 17:09 [PATCH 0/2] ARM: dts: am5729: beaglebone-ai: Enable BeagleBone AI Caleb Robey
2019-11-14 17:09 ` [PATCH 1/2] ARM: dts: am5729: beaglebone-ai: dra7 reqs in dts Caleb Robey
2019-11-14 17:47 ` Tony Lindgren [this message]
2019-11-14 17:09 ` [PATCH 2/2] ARM: dts: am5729: beaglebone-ai: adding device tree Caleb Robey
2019-11-18 11:33 ` Grygorii Strashko
-- strict thread matches above, loose matches on Subject: below --
2019-11-14 17:06 [PATCH 0/2] ARM: dts: am5729: beaglebone-ai: Enable BeagleBone AI Caleb Robey
2019-11-14 17:06 ` [PATCH 1/2] ARM: dts: am5729: beaglebone-ai: dra7 reqs in dts Caleb Robey
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=20191114174705.GV5610@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=lokeshvutla@ti.com \
--cc=mark.rutland@arm.com \
--cc=praneeth@ti.com \
--cc=robh+dt@kernel.org \
--cc=trini@konsulko.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).