From: Tom <Tom.Rix@windriver.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [STATUS] Merge Window closed, waiting for pull requests
Date: Fri, 05 Feb 2010 09:02:17 -0600 [thread overview]
Message-ID: <4B6C32F9.2060106@windriver.com> (raw)
In-Reply-To: <1687fa361002050105xd1fc860v331100c73de4770@mail.gmail.com>
Dirk Behme wrote:
> On Thu, Feb 4, 2010 at 8:30 PM, Paulraj, Sandeep <s-paulraj@ti.com> wrote:
>>
>>> On 20.01.2010 18:58, Paulraj, Sandeep wrote:
>>>>
>>>>> Subject: Re: [U-Boot] [STATUS] Merge Window closed, waiting for pull
>>>>> requests
>>>>>
>>>>> On 19.01.2010 23:30, Wolfgang Denk wrote:
>>>>>> Hi
>>>>>>
>>>>>> as you probably have noticed, the merge window closed about 24 hours
>>>>>> ago. Checking my list, I still see s _long_ list of ARM related
>>>>>> patches that have not been processed yet. For many of them I haven't
>>>>>> seen any review comments, nor have architecture maintainer picked
>>>>>> these up and sent pull requests to Tom.
>>>>>>
>>>>>> Can you please try and work on this now, so that we can have the
>>>>>> outstanding patches integrated into mainline in the next few days?
>>>>> I'd like to see the Beagle rev C4 patches applied:
>>>>>
>>>>> http://lists.denx.de/pipermail/u-boot/2010-January/066629.html
>>>>> http://lists.denx.de/pipermail/u-boot/2010-January/066632.html
>>>>> http://lists.denx.de/pipermail/u-boot/2010-January/066634.html
>>>>> http://lists.denx.de/pipermail/u-boot/2010-January/066636.html
>>>>> http://lists.denx.de/pipermail/u-boot/2010-January/066638.html
>>>>> http://lists.denx.de/pipermail/u-boot/2010-January/066640.html
>>>>> http://lists.denx.de/pipermail/u-boot/2010-January/066642.html
>>>>>
>>>>> (The ml archive seems to have some issues with these patches. In my
>>>>> inbox they seem to be fine, though)
>>>> Same with me but when I discussed offline with Tom, it appears as if
>>> this set never made it to his Inbox.
>>>> We need just a little more time.
>>> What's the recent status of this?
>> Tom had comments.
>
> Do you (or anybody else) mind to send the archive links of the
> comments? Just to be sure that everything will be covered and nothing
> is missed ;)
>
> Many thanks and best regards
>
> Dirk
The big ones I remember are copyrights, documenting magic video settings, clk
tweeking needs to move to board level.
These weren't all of them, please see my full comments on 1/23
Tom
next prev parent reply other threads:[~2010-02-05 15:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-19 22:30 [U-Boot] [STATUS] Merge Window closed, waiting for pull requests Wolfgang Denk
2010-01-19 23:26 ` Mike Frysinger
2010-01-20 12:58 ` Wolfgang Denk
2010-01-21 5:32 ` Mike Frysinger
2010-01-21 21:27 ` Wolfgang Denk
2010-01-22 0:32 ` Mike Frysinger
2010-01-22 11:57 ` Wolfgang Denk
2010-01-20 17:44 ` Dirk Behme
2010-01-20 17:58 ` Paulraj, Sandeep
2010-01-20 18:50 ` Dirk Behme
2010-01-21 13:58 ` Tom
2010-02-04 18:04 ` Dirk Behme
2010-02-04 19:30 ` Paulraj, Sandeep
2010-02-05 9:05 ` Dirk Behme
2010-02-05 15:02 ` Tom [this message]
2010-02-05 16:09 ` John Rigby
2010-02-07 10:44 ` [U-Boot] OMAP3 Beagle patches (was: Merge Window closed, waiting for pull request) Dirk Behme
2010-02-08 7:05 ` Khasim Syed Mohammed
2010-01-21 8:27 ` [U-Boot] [STATUS] Merge Window closed, waiting for pull requests Vipin Kumar
2010-01-21 9:55 ` Armando VISCONTI
2010-01-21 21:58 ` Wolfgang Denk
2010-01-21 21:56 ` Wolfgang Denk
2010-01-21 22:00 ` Paulraj, Sandeep
2010-01-22 3:54 ` Vipin Kumar
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=4B6C32F9.2060106@windriver.com \
--to=tom.rix@windriver.com \
--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