From: Tom <Tom.Rix@windriver.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] ARM pull request v3
Date: Tue, 20 Oct 2009 07:24:32 -0500 [thread overview]
Message-ID: <4ADDAC00.1080804@windriver.com> (raw)
In-Reply-To: <4ADC7A02.4060508@googlemail.com>
Dirk Behme wrote:
> Tom wrote:
>> This is what has changed since v2
>>
>> 10,12c10,12
>> < CPU9260 : fix machine ID when using a CPU9G20.
>> < fix CPU9260/CPU9G20 compile warnings
>> < main.c: In function 'abortboot':
>> ---
>> > AT91 CPU9260 Fix machine ID when using a CPU9G20.
>> > AT91 CPU9260 CPU9G20 Fix compile warnings
>> > AT91 CPUAT91 Fix compiler warning
>> 45,46c45
>> < Steve Sakoman (2):
>> < TI: OMAP3: Refactors the SM911x driver
>> ---
>> > Steve Sakoman (1):
>> 117d115
>> < drivers/net/smc911x.c | 12 +-
>> 161c159
>>
>> This comes from rebasing the arm master-sync branch
>
> ...
>
>> I removed the sm911x patch.
>
> After this is discussed now, could we apply it again?
>
> Without this patch it will be broken.
>
I believe the issue is only about the workflow process of the patch.
I believe to resolve, the patch needs to be reposted, unchanged, to the
list and to have Ben's ack-ed by added.
Once this is done, I can apply it.
Tom
> Thanks
>
> Dirk
next prev parent reply other threads:[~2009-10-20 12:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-18 22:58 [U-Boot] ARM pull request v3 Tom
2009-10-19 0:37 ` Paulraj, Sandeep
2009-10-19 1:53 ` Ben Warren
2009-10-19 8:33 ` Wolfgang Denk
2009-10-19 14:38 ` Dirk Behme
2009-10-20 12:24 ` Tom [this message]
2009-10-23 9:28 ` Simon Kagstrom
2009-10-23 13:02 ` Tom
-- strict thread matches above, loose matches on Subject: below --
2009-10-13 12:55 Tom Rix
2009-10-13 13:34 ` Abdoulaye Walsimou Gaye
2009-10-13 14:04 ` Wolfgang Denk
2009-10-13 14:40 ` Paulraj, Sandeep
2009-10-13 14:51 ` Wolfgang Denk
2009-10-13 14:58 ` Simon Kagstrom
2009-10-14 11:18 ` Tom Rix
2009-10-14 11:54 ` Simon Kagstrom
2009-10-13 16:01 ` Dirk Behme
2009-10-13 16:08 ` Paulraj, Sandeep
2009-10-17 5:52 ` Dirk Behme
2009-10-17 13:25 ` Paulraj, Sandeep
2009-10-17 14:22 ` Tom
2009-10-17 22:16 ` Tom
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=4ADDAC00.1080804@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