From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] ARM: add basic support for the Broadcom BCM2835 SoC
Date: Fri, 22 Jun 2012 12:30:26 -0600 [thread overview]
Message-ID: <4FE4B9C2.3050001@wwwdotorg.org> (raw)
In-Reply-To: <20120622181854.399B520225A@gemini.denx.de>
On 06/22/2012 12:18 PM, Wolfgang Denk wrote:
> Dear Stephen Warren,
>
> In message <4FE4AB87.1030500@wwwdotorg.org> you wrote:
>>
>>> For which sub-system to you volunteer to become the custodian?
>>
>> The BCM2835 ARM sub-architecture, as used in the Raspberry Pi.
>
> I see no reason to install a new custodian just for a single SoC.
OK, that's fine; I'll rely solely on patch email then. I just figured on
saving Albert some git am work, seeing as how many other single SoCs are
handled via git pull already.
next prev parent reply other threads:[~2012-06-22 18:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-07 5:45 [U-Boot] [PATCH 1/2] ARM: add basic support for the Broadcom BCM2835 SoC Stephen Warren
2012-06-07 5:45 ` [U-Boot] [PATCH 2/2] ARM: bcm2835: add Raspberry Pi model B board Stephen Warren
2012-06-16 5:42 ` Graeme Russ
2012-06-18 3:54 ` Stephen Warren
2012-06-16 3:52 ` [U-Boot] [PATCH 1/2] ARM: add basic support for the Broadcom BCM2835 SoC Stephen Warren
2012-06-21 22:26 ` Stephen Warren
2012-06-22 5:05 ` Albert ARIBAUD
2012-06-22 16:23 ` Stephen Warren
2012-06-22 16:34 ` Wolfgang Denk
2012-06-22 16:36 ` Stephen Warren
2012-06-22 17:14 ` Wolfgang Denk
2012-06-22 17:29 ` Stephen Warren
2012-06-22 17:34 ` Tom Rini
2012-06-22 18:18 ` Wolfgang Denk
2012-06-22 18:30 ` Stephen Warren [this message]
2012-06-22 21:58 ` Wolfgang Denk
2012-06-22 23:18 ` Stephen Warren
2012-06-22 23:28 ` Wolfgang Denk
2012-06-22 23:31 ` Tom Rini
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=4FE4B9C2.3050001@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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