public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Warren <TWarren@nvidia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Tegra U-Boot Patches
Date: Thu, 10 May 2018 23:08:26 +0000	[thread overview]
Message-ID: <a5334b3569bb4236a74e0417ccd2ae8d@HQMAIL101.nvidia.com> (raw)
In-Reply-To: <1525992045.9249.36.camel@ziswiler.com>

Hi, Marcel.  I had it on my TODO list to send you an email asking for a list of pending patches today!  Sorry for the delay - things have heated up here and I don’t get to give my upstream tasks as much attention as I'd like.

I'll pull them down first thing tomorrow and get a PR up for TomR to apply.  Are they in order as you have them listed here? i.e. I can apply #1, then #2, then #3? Or are there no dependencies?

Thanks for your patience,

Tom

-----Original Message-----
From: Marcel Ziswiler <marcel@ziswiler.com> 
Sent: Thursday, May 10, 2018 3:41 PM
To: Tom Warren <TWarren@nvidia.com>
Cc: Tom Rini <trini@konsulko.com>; u-boot at lists.denx.de; Marcel Ziswiler <marcel.ziswiler@toradex.com>
Subject: Tegra U-Boot Patches

Hi Tom

I have 3 patch sets [1, 2, 3] more or less long since (e.g. the longest almost one full year now) awaiting inclusion. Could you please consider pulling those in during current merge window?

Good news two more patches [4, 5] long since got applied and may be removed (resp. status changes) in patchwork.

[1] https://patchwork.ozlabs.org/project/uboot/list/?series=43045
[2] https://patchwork.ozlabs.org/project/uboot/list/?series=43210
[3] https://patchwork.ozlabs.org/project/uboot/list/?series=43290
[4] https://patchwork.ozlabs.org/patch/797890/
[5] https://patchwork.ozlabs.org/patch/797887/

Thanks!

Cheers

Marcel

-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information.  Any unauthorized review, use, disclosure or distribution
is prohibited.  If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------

  parent reply	other threads:[~2018-05-10 23:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-10 22:40 [U-Boot] Tegra U-Boot Patches Marcel Ziswiler
2018-05-10 22:43 ` Tom Rini
2018-05-10 23:39   ` Tom Warren
2018-05-10 23:08 ` Tom Warren [this message]
2018-05-10 23:20   ` Marcel Ziswiler

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=a5334b3569bb4236a74e0417ccd2ae8d@HQMAIL101.nvidia.com \
    --to=twarren@nvidia.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