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] Tegra USB driver movement
Date: Mon, 01 Oct 2012 08:50:46 +0200	[thread overview]
Message-ID: <1349074246.1454.4.camel@tellur> (raw)
In-Reply-To: <201210010417.53926.marex@denx.de>

Also CC'ing Albert

Am Montag, den 01.10.2012, 04:17 +0200 schrieb Marek Vasut:
> Dear Lucas Stach,
> 
> > Hi all,
> > 
> > now that everything involving Colibri T20 is in pretty good shape I'm
> > moving on to some code cleanups to the U-Boot Tegra codebase.
> > 
> > One of the big things on my list is the move of the Tegra USB driver
> > implementation to the correct location in drivers/usb/host. In
> > anticipation of this move all USB related changes for the next merge
> > window have already gone through the u-boot-usb tree to minimize
> > conflicts.
> 
> I think I'll push them into -next once builds are done.
> 
> > Now with the mass renaming of Tegra header files for the Tegra 3
> > clearing we have another situation which makes the move harder to do
> > without breaking the build of either the u-boot-usb or u-boot-tegra
> > tree. However we can easily solve that with some proper coordination.
> > 
> > So the  plan is a follows:
> > The mass renaming of the Tegra header files did not generate any back
> > push from developers involved in Tegra. So if Tom is confident that this
> > change is good to go, I would like him to do a pull request to
> > u-boot-arm as soon as possible. On IRC Albert already expressed his plan
> > to do another pull request to u-boot master by Thursday latest. If we
> > could get in the mass rename into this pull request it would be really
> > great, as it would allow to sync the u-boot-usb tree with the current
> > Tegra work in the next week. Once this is done we can easily move the
> > Tegra USB driver without breaking anything.
> > 
> > Would this be ok with everyone?
> 
> Sorry, all the usb changes go to -next.
> 
Right all things that we are talking about here are going into the
respective next trees. Sorry for the confusion. The plan still holds,
except I'm not sure if Albert is also going to do a P-R for
u-boot-arm/next, so CC'ing him to let him know that we might also need
some help from his side.

> > Thanks,
> > Lucas
> 
> Best regards,
> Marek Vasut
> 

  reply	other threads:[~2012-10-01  6:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-01  0:22 [U-Boot] Tegra USB driver movement Lucas Stach
2012-10-01  2:17 ` Marek Vasut
2012-10-01  6:50   ` Lucas Stach [this message]
2012-10-01 16:38     ` Tom 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=1349074246.1454.4.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