From: rmallon@gmail.com (Ryan Mallon)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] DEBUG_LL platform updates for 3.2
Date: Fri, 14 Oct 2011 10:09:14 +1100 [thread overview]
Message-ID: <4E976F9A.80203@gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1110130932350.17040@xanadu.home>
On 14/10/11 00:39, Nicolas Pitre wrote:
> On Thu, 13 Oct 2011, Russell King - ARM Linux wrote:
>
>> On Wed, Oct 12, 2011 at 10:30:11AM +0200, Arnd Bergmann wrote:
>>> On Tuesday 11 October 2011 20:03:38 Nicolas Pitre wrote:
>>>> On Tue, 11 Oct 2011, Arnd Bergmann wrote:
>>>>
>>>>> I've stuck them into the arm-soc tree for now, so we get linux-next
>>>>> coverage, but I won't send them to Linus this way because then we
>>>>> would get the same commits twice in the history.
>>>>
>>>> Could you please do the same with the following:
>>>>
>>>> git://git.linaro.org/people/nico/linux.git mach_memory_h
>>>>
>>>> Russell pulled it at some point, and dropped it due to concerns about
>>>> repeated conflict resolutions (or so I presume). I just did a test
>>>> merge between your for-next branch and the above and that looked trivial
>>>> enough.
>>>
>>> Ok, done.
>>
>> Bypassing maintainers stinks - especially when there are unaddressed
>> comments outstanding. Nicolas has "simplified" my objections in this
>> request for you to pull - and has completely ignored the problem that
>> it breaks ZBOOT_ROM by deleting the zreladdr definitions on EP93xx
>> with no way for that to be provided.
>
> I also told you that EP93xx doesn't use ZBOOT_ROM anywhere, and that
> this was approved by the EP93xx maintainers.
As the less active of the two EP93xx maintainers I didn't agree to this.
I don't know if Hartley did, but I can't find anything from him in a
quick search of the list. I have Cc'ed him.
I don't have time to follow this issue in depth, but from my vague
understanding ZBOOT_ROM is unlikely to be used on EP93xx, but still
_possible_ to use. Therefore we should not be removing support for
ZBOOT_ROM on EP93xx in case there are some users out there.
~Ryan
next prev parent reply other threads:[~2011-10-13 23:09 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 10:38 [GIT PULL] DEBUG_LL platform updates for 3.2 Will Deacon
2011-10-03 8:35 ` Will Deacon
2011-10-07 20:51 ` Arnd Bergmann
2011-10-10 10:36 ` Will Deacon
2011-10-10 11:20 ` Arnd Bergmann
2011-10-10 13:32 ` Will Deacon
2011-10-11 7:52 ` Shawn Guo
2011-10-11 13:33 ` Arnd Bergmann
2011-10-11 15:09 ` Will Deacon
2011-10-11 18:48 ` Will Deacon
2011-10-11 19:25 ` Arnd Bergmann
2011-10-12 0:03 ` Nicolas Pitre
2011-10-12 8:30 ` Arnd Bergmann
2011-10-13 8:28 ` Russell King - ARM Linux
2011-10-13 13:39 ` Nicolas Pitre
2011-10-13 14:05 ` Russell King - ARM Linux
2011-10-13 18:36 ` Nicolas Pitre
2011-10-13 14:50 ` Arnd Bergmann
2011-10-13 23:09 ` Ryan Mallon [this message]
2011-10-13 23:40 ` Ryan Mallon
2011-10-14 2:32 ` Nicolas Pitre
2011-10-12 8:38 ` Jamie Iles
2011-10-12 20:16 ` Nicolas Pitre
2011-10-13 8:23 ` Russell King - ARM Linux
2011-10-13 18:46 ` Nicolas Pitre
2011-10-12 17:29 ` Russell King - ARM Linux
2011-10-12 17:35 ` Will Deacon
2011-10-12 18:01 ` Russell King - ARM Linux
2011-10-12 18:05 ` Will Deacon
2011-10-17 8:25 ` Russell King - ARM Linux
2011-10-17 9:23 ` Will Deacon
2011-10-20 14:57 ` Arnd Bergmann
2011-10-21 10:59 ` Will Deacon
2011-10-21 14:48 ` Rob Herring
2011-10-21 15:11 ` Arnd Bergmann
2011-10-21 15:15 ` Will Deacon
2011-10-21 18:03 ` Rob Herring
2011-10-21 23:04 ` Rob Herring
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=4E976F9A.80203@gmail.com \
--to=rmallon@gmail.com \
--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).