From: dwalker@codeaurora.org (Daniel Walker)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Initial Tegra ARM support
Date: Thu, 05 Aug 2010 15:14:23 -0700 [thread overview]
Message-ID: <1281046463.30969.14.camel@c-dwalke-linux.qualcomm.com> (raw)
In-Reply-To: <AANLkTimZYveOZLoDS82z0nosAHa21ChHCK1GpophEQ1P@mail.gmail.com>
On Thu, 2010-08-05 at 15:01 -0700, Erik Gilling wrote:
> If these changes went through Russell's tree there would be
> dependancies on arch/arm/mach-tegra/(Makefile|Kconfig) in
> arch/arm/(Makefile|Kconfig) breaking Russell's tree until it was
> merged with the tegra tree. That sounds wrong to me. Additionally
> these patches have received review on LAKML including some by Russell
> and nothing was mentioned about this being a problem.
It's wrong to do it the way your suggesting .. You don't need to create
conflicts when you send stuff to Russell.. It takes some skill to break
things up by maintainer, but you need to learn how to do that in order
to play nice with the other ARM sub-architecture maintainers ..
If you have some questions on how to break stuff up feel free to ask me,
or send questions to the linux-arm-kernel list ..
Daniel
--
Sent by an consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2010-08-05 22:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 21:10 [GIT PULL] Initial Tegra ARM support Erik Gilling
2010-08-05 21:45 ` Daniel Walker
2010-08-05 22:01 ` Erik Gilling
2010-08-05 22:06 ` Erik Gilling
2010-08-05 22:14 ` Daniel Walker [this message]
2010-08-10 21:44 ` Daniel Walker
2010-08-10 22:06 ` Russell King - ARM Linux
2010-08-10 22:10 ` Daniel Walker
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=1281046463.30969.14.camel@c-dwalke-linux.qualcomm.com \
--to=dwalker@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).