From: zonque@gmail.com (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: Current state of AM33xx patches
Date: Mon, 25 Jun 2012 20:17:27 +0200 [thread overview]
Message-ID: <4FE8AB37.7030907@gmail.com> (raw)
In-Reply-To: <4FE326A8.8090807@gmail.com>
On 21.06.2012 15:50, Daniel Mack wrote:
> On 18.06.2012 10:15, Hiremath, Vaibhav wrote:
>> On Mon, Jun 11, 2012 at 19:21:21, Jason Kridner wrote:
>>> From: Daniel Mack <zonque@gmail.com>
>>>> Hey,
>>>>
>>>> can anybody give me a quick wrap-up about the current state of AM33xx
>>>> based SoCs in mainline? What are the next steps to get things merged?
>>>
>>> There is a wiki page [1] that is intended to provide a summary, but I'm
>>> confident it is not up-to-date.
>>
>> Page updated now...
>>
>> http://processors.wiki.ti.com/index.php/Sitara_Linux_Upstream_Status#AM335x_Linux_Status
>
> Great, thanks. So if things get upstreamed, which is the repo/branch
> they appear in? In other words: where is the code people should write
> patches against? I couldn't find an answer to that yet.
ping?
next prev parent reply other threads:[~2012-06-25 18:17 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 9:28 Current state of AM33xx patches Daniel Mack
2012-06-11 13:51 ` Jason Kridner
2012-06-11 14:21 ` Hernandez, Carlos
2012-06-18 8:15 ` Hiremath, Vaibhav
2012-06-21 13:50 ` Daniel Mack
2012-06-25 18:17 ` Daniel Mack [this message]
2012-06-26 11:42 ` Sekhar Nori
2012-06-27 12:13 ` Hiremath, Vaibhav
2012-06-28 15:09 ` Daniel Mack
2012-06-29 13:54 ` Yegor Yefremov
2012-06-29 17:43 ` Hiremath, Vaibhav
2012-07-02 12:56 ` Yegor Yefremov
2012-06-29 17:33 ` Hiremath, Vaibhav
2012-06-29 18:34 ` Daniel Mack
2012-06-29 18:47 ` Hiremath, Vaibhav
2012-06-30 2:11 ` Paul Walmsley
2012-06-30 9:33 ` Daniel Mack
2012-07-04 10:07 ` Paul Walmsley
2012-07-04 10:50 ` Hiremath, Vaibhav
2012-07-04 11:22 ` Daniel Mack
2012-07-05 17:45 ` N, Mugunthan V
2012-07-23 6:30 ` Daniel Mack
2012-07-23 16:36 ` N, Mugunthan V
2012-07-26 14:52 ` Daniel Mack
2012-07-26 15:00 ` Koen Kooi
2012-07-26 15:58 ` Daniel Mack
2012-07-26 16:09 ` Koen Kooi
2012-07-26 17:46 ` Daniel Mack
2012-07-31 19:29 ` Koen Kooi
2012-08-02 15:30 ` Daniel Mack
2012-08-02 15:37 ` Koen Kooi
2012-08-02 17:19 ` Daniel Mack
2012-08-02 19:56 ` Daniel Mack
2012-08-02 20:20 ` Koen Kooi
2012-08-03 10:17 ` N, Mugunthan V
2012-08-03 5:25 ` N, Mugunthan V
2012-06-11 14:15 ` Vaibhav Hiremath
2012-06-23 13:03 ` Domenico Andreoli
2012-06-27 12:07 ` Hiremath, Vaibhav
2012-06-27 18:31 ` Paul Walmsley
2012-06-27 19:01 ` Hiremath, Vaibhav
2012-06-27 19:12 ` Paul Walmsley
2012-06-27 19:21 ` Hiremath, Vaibhav
2012-06-27 19:37 ` Paul Walmsley
2012-06-27 20:00 ` Paul Walmsley
2012-06-27 20:56 ` Hiremath, Vaibhav
2012-06-27 21:13 ` Paul Walmsley
2012-06-27 21:44 ` Paul Walmsley
2012-06-29 14:20 ` Mark Jackson
2012-06-29 17:56 ` Hiremath, Vaibhav
2012-07-02 8:04 ` Mark Jackson
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=4FE8AB37.7030907@gmail.com \
--to=zonque@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).