Arnd,
This is my first pull request for Tegra; hopefully it all works out OK!
Note: Nobody has ack'd this change. I'm a maintainer for the files that
are touched, but I'm not sure if maintainers are supposed to have
another maintainer ack the change before committing it and sending a
pull request (in particular for their own changes), or if it's up to
their discretion?
The following changes since commit c16fa4f2ad19908a47c63d8fa436a1178438c7e7:
Linus Torvalds (1):
Linux 3.3
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/swarren/linux-tegra.git
for-3.4/fixes-for-rc1-and-v3.3
Stephen Warren (1):
ARM: tegra: Fix device tree AUXDATA for USB/EHCI
arch/arm/mach-tegra/board-dt-tegra20.c | 6 +++---
arch/arm/mach-tegra/devices.c | 7 +++----
arch/arm/mach-tegra/devices.h | 5 +++++
3 files changed, 11 insertions(+), 7 deletions(-)
On Wednesday 21 March 2012, Stephen Warren wrote:
This is my first pull request for Tegra; hopefully it all works out OK!
Note: Nobody has ack'd this change. I'm a maintainer for the files that
are touched, but I'm not sure if maintainers are supposed to have
another maintainer ack the change before committing it and sending a
pull request (in particular for their own changes), or if it's up to
their discretion?
Hi Stephen,
The pull request looks good. There is no need for anyone else to ack
your patches, but you should always post them on the appropriate
mailing lists so people can weigh in if they see something wrong.
I'm currently trying to get the first set of my v3.4 pull requests
out to Linus, so I'll apply this when I'm done with that.
Arnd
On Wed, Mar 21, 2012 at 06:30:24PM +0000, Arnd Bergmann wrote:
On Wednesday 21 March 2012, Stephen Warren wrote:
quoted
This is my first pull request for Tegra; hopefully it all works out OK!
Note: Nobody has ack'd this change. I'm a maintainer for the files that
are touched, but I'm not sure if maintainers are supposed to have
another maintainer ack the change before committing it and sending a
pull request (in particular for their own changes), or if it's up to
their discretion?
Hi Stephen,
The pull request looks good. There is no need for anyone else to ack
your patches, but you should always post them on the appropriate
mailing lists so people can weigh in if they see something wrong.
I'm currently trying to get the first set of my v3.4 pull requests
out to Linus, so I'll apply this when I'm done with that.
I've started staging the first batch of fixes for 3.4-rc, and I've pulled this
into that branch. Thanks, Stephen.
-Olof