From: computersforpeace@gmail.com (Brian Norris)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] mach-bcm: brcmstb platform support for 3.17
Date: Mon, 28 Jul 2014 23:02:07 -0700 [thread overview]
Message-ID: <20140729060207.GB11952@brian-ubuntu> (raw)
In-Reply-To: <20140728143126.GB2593@beef>
On Mon, Jul 28, 2014 at 10:31:26AM -0400, Matt Porter wrote:
> I applied all but "ARM: brcmstb: add debug UART for earlyprintk support"
> to mach-bcm for-3.17/[soc|dt]. That patch should also go through
> Russell.
Thanks for the tip. I just submitted the earlyprintk patch to Russel.
> Also, pull requests are fine, but it will help greatly to have pull
> requests split into the appropriate arm-soc categories next time. I
> split these into soc and dt as that is how they need to go to the
> arm-soc team.
Sure thing. In the future, I may just stick with patches, and you can
queue them how you'd like.
Is the arm-soc development process documented somewhere? Like an FAQ, or
ANNOUNCEMENT? [1] I understand that it's a large and noisy subsystem
that warrants some additional processes of its own (beyond what I've
seen in other subsystems), but as a relative newcomer to participating
in it, I've only been able to glean a few bits of info from searching
the LKML/linux-arm-kernel archives.
If not, I'm sure I'll figure things out eventually.
Thanks,
Brian
[1] This comes close. At least it captures the history:
http://elinux.org/images/a/ad/Arm-soc-checklist.pdf
prev parent reply other threads:[~2014-07-29 6:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 23:25 [GIT PULL] mach-bcm: brcmstb platform support for 3.17 Brian Norris
2014-07-28 14:31 ` Matt Porter
2014-07-29 6:02 ` Brian Norris [this message]
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=20140729060207.GB11952@brian-ubuntu \
--to=computersforpeace@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).