public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Lucas Stach <dev@lynxeye.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] tegra: add ULPI on USB2 funcmux entry
Date: Thu, 31 May 2012 21:43:04 +0200	[thread overview]
Message-ID: <1338493384.31497.10.camel@tellur> (raw)
In-Reply-To: <5FBF8E85CA34454794F0F7ECBA79798F379C416005@HQMAIL04.nvidia.com>

Hi Tom,
Am Donnerstag, den 31.05.2012, 08:47 -0700 schrieb Tom Warren:
> Lucas,
> 
> > -----Original Message-----
> > From: Lucas Stach [mailto:dev at lynxeye.de]
> > Sent: Thursday, May 31, 2012 4:51 AM
> > To: u-boot at lists.denx.de
> > Cc: Stephen Warren; Tom Warren
> > Subject: [PATCH 1/2] tegra: add ULPI on USB2 funcmux entry
> 
> This should be a [PATCH V2 1/2], if you are dropping the RAM size patch from the series (so I can keep track of which patches are the latest and should be applied to u-boot-tegra).  Please see the 'Patches' entry on the U-Boot wiki, specifically 'Sending updated patch versions'.
> 
Yes, I intend to drop the first patch, as my need to support multiple
RAM configurations with a single u-boot image is addressed by your patch
to load the ODMDATA from the BCT.
Though I still dislike this duplication of information between MC config
and ODMDATA, but I think it's a waste of time to argue about this, as it
is way above my head.

Sorry for not properly versioning those two patches, I'll do so in the
future.

Thanks,
Lucas

      parent reply	other threads:[~2012-05-31 19:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-31 11:51 [U-Boot] [PATCH 1/2] tegra: add ULPI on USB2 funcmux entry Lucas Stach
2012-05-31 11:51 ` [U-Boot] [PATCH 2/2] tegra: usb: fix wrong error check Lucas Stach
2012-05-31 13:14   ` Marek Vasut
2012-05-31 17:44   ` Stephen Warren
     [not found] ` <5FBF8E85CA34454794F0F7ECBA79798F379C416005@HQMAIL04.nvidia.com>
2012-05-31 19:43   ` Lucas Stach [this message]

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=1338493384.31497.10.camel@tellur \
    --to=dev@lynxeye.de \
    --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