From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH] ARM: tegra: Add NVIDIA Jetson Nano Developer Kit support
Date: Wed, 25 Mar 2020 14:30:03 -0400 [thread overview]
Message-ID: <20200325183003.GU5793@bill-the-cat> (raw)
In-Reply-To: <BYAPR12MB26000F8C9E95B0E6068941C5C1CE0@BYAPR12MB2600.namprd12.prod.outlook.com>
On Wed, Mar 25, 2020 at 06:28:20PM +0000, Tom Warren wrote:
>
>
> -----Original Message-----
> From: Tom Rini <trini@konsulko.com>
> Sent: Wednesday, March 25, 2020 11:26 AM
> To: Tom Warren <TWarren@nvidia.com>
> Cc: Peter Robinson <pbrobinson@gmail.com>; u-boot at lists.denx.de; Stephen Warren <swarren@nvidia.com>; Thierry Reding <treding@nvidia.com>; Jonathan Hunter <jonathanh@nvidia.com>; tomcwarren3959 at gmail.com
> Subject: Re: [PATCH] ARM: tegra: Add NVIDIA Jetson Nano Developer Kit support
>
> On Wed, Mar 25, 2020 at 06:24:43PM +0000, Tom Warren wrote:
>
> > > That is strange, please re-post them and we'll see what happens. If they don't show up right away I can poke people. Thanks!
> >
> > Just resent the Nano patch via:
> >
> > git send-email 0001*.patch --to u-boot at lists.denx.de --confirm always
> > --annotate --from tomcwarren3959 at gmail.com --cc swarren at nvidia.com
> > --cc treding at nvidia.com --cc jonathanh at nvidia.com --cc
> > twarren at nvidia.com
> >
> > This time I used my Gmail address in 'from' and put my work address in 'cc'.
> >
> > Let's see if it shows up in Patchwork.
>
> There's http://patchwork.ozlabs.org/patch/1261582/ now, just that one patch?
> [Tom] yes, the one I resent above, but using my gmail address (tomcwarren3959) instead of my work address (twarren at nvidia.com). Any idea why that would make any difference?
> I'll work on resending the others using that address.
Not sure what went wrong, sorry.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200325/b15fecc6/attachment.sig>
next prev parent reply other threads:[~2020-03-25 18:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 19:03 [PATCH] ARM: tegra: Add NVIDIA Jetson Nano Developer Kit support twarren at nvidia.com
2020-03-25 12:52 ` Peter Robinson
2020-03-25 17:44 ` Tom Warren
2020-03-25 17:55 ` Tom Rini
2020-03-25 18:24 ` Tom Warren
2020-03-25 18:26 ` Tom Rini
2020-03-25 18:28 ` Tom Warren
2020-03-25 18:30 ` Tom Rini [this message]
2020-03-25 19:30 ` Stephen Warren
2020-03-25 20:22 ` Tom Warren
-- strict thread matches above, loose matches on Subject: below --
2020-03-25 18:21 tomcwarren3959 at gmail.com
2020-04-01 22:31 ` Peter Robinson
2020-04-01 22:57 ` Tom Warren
2020-04-01 23:05 ` Stephen Warren
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=20200325183003.GU5793@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.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