public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Tegra: T1x4: SPI: Use a common name (t1x4) for SPI driver
Date: Tue, 08 Oct 2013 15:20:48 -0600	[thread overview]
Message-ID: <52547730.5090409@wwwdotorg.org> (raw)
In-Reply-To: <CA+m5__JHwSdSAc5FZ56ATmkVndYzO6uJu2jrK0KEhb=EF=z16g@mail.gmail.com>

On 10/08/2013 10:03 AM, Tom Warren wrote:
> On Mon, Oct 7, 2013 at 11:23 PM, Jagan Teki <jagannadh.teki@gmail.com> wrote:
>> On Tue, Oct 8, 2013 at 2:50 AM, Tom Warren <twarren.nvidia@gmail.com> wrote:
>>> Tegra124 is compatible w/T114 SPI, so try to commonize as
>>> much as possible.
>>>
>>> TEST=built all T1x4 boards, tested on Venice1 & 2 OK.
>>> There's no real binary change here, just names/includes.
...
>> Is it part of tegra.git?
>>
> I'm not sure what you are asking here. This code will go in to
> u-boot-tegra/next when it's Acked, if that's what you mean. It only affects
> Tegra SPI, so it doesn't need to go thru the SPI repo (no functional
> change, just a rename for future SoCs).

SPI patches should be applied to the SPI tree, not the Tegra tree. the
various subsystem trees exist to accept the patches for those subsystems...

  parent reply	other threads:[~2013-10-08 21:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-07 21:20 [U-Boot] [PATCH] Tegra: T1x4: SPI: Use a common name (t1x4) for SPI driver Tom Warren
2013-10-08  6:23 ` Jagan Teki
2013-10-08 16:03   ` Tom Warren
2013-10-08 16:08     ` Jagan Teki
2013-10-08 21:20     ` Stephen Warren [this message]
2013-10-08 21:19   ` Stephen Warren
2013-10-09 13:32     ` Jagan Teki
2013-10-08 16:13 ` Jagan Teki
2013-10-08 21:23 ` 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=52547730.5090409@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --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