From: Graeme Russ <graeme.russ@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] x86 cleanup patches
Date: Mon, 07 Nov 2011 06:46:13 +1100 [thread overview]
Message-ID: <4EB6E405.4060509@gmail.com> (raw)
In-Reply-To: <20111106190904.AF7951893012@gemini.denx.de>
Hi Wolfgang,
On 07/11/11 06:09, Wolfgang Denk wrote:
> Dear Graeme Russ,
>
> In message <4EB67A6E.2090902@gmail.com> you wrote:
>>
>> I have two x86 tidy-up patch series that I intend to apply in the next 2-3
>> weeks to a 'next' branch on the x86 repo. Being 'next', these patches are
>> intended for the current merge window which closes on December 12
>
> You confuse me.
>
> Currently the merge window is closed. The next release is scheduled
> for December 12. ONly then, the _next_ merge window will open.
Oops, what you're saying is what I meant - next merge window
>> Please be aware that the latest series (checkpatch cleanup) is designed to
>> be applied first, but it was actually created _after_ the 'Various x86
>> cleanups' series and hence, there is a wee little bit of incompatibility
>> between the two (and silly me should have called the latest one v0 as
>> well...). The conflicts aren't so bad - I already have them resolved but
>> the second series is not checkpatch clean yet. Before I apply this series
>> to 'next' I will be posting a unified patch set in the next week or so - It
>> will be a 12 part series which will line up 1-to-1 so I'll be setting the
>> in-reply-to to thread from the current patches. In the meantime, please:
>
> This being mostly cleanup, and we still being relatively early in the
> stabilization phase, I would also accept this stuff now.
OK - There is only one patch that adds new 'features' - The 'Add multiboot
header' but that's just some canned static data, no code
>> 1) Have a look at the two independent series and let me know if there is
>> any glaring issues I need to address
>
> I will, time permitting.
Thanks
>> 2) Let me know if you need more than two weeks
>
> ?
>
>> 3) Be prepared to rebase any current x86 patches against 'next' in three
>> weeks time (unless otherwise informed)
>
> ?
>
>> Gabe, going by this schedule, there will be a good two weeks between the
>> x86 cleanup hitting 'next' and the merge window closing - I think this
>
> Which merge window are you talking about?
Sorry for the confusion - I intend to get Gabe's patches into x86/next as
soon as the next merge window opens on December 12
Regards,
Graeme
next prev parent reply other threads:[~2011-11-06 19:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-06 12:15 [U-Boot] x86 cleanup patches Graeme Russ
2011-11-06 19:09 ` Wolfgang Denk
2011-11-06 19:46 ` Graeme Russ [this message]
2011-11-06 19:50 ` Wolfgang Denk
2011-11-06 21:22 ` Graeme Russ
[not found] ` <CAPPXG1=tNvQX8P01DA5gwcwc7k7VuSa7xE+unQQj6rMW14omdg@mail.gmail.com>
2011-11-13 9:48 ` Graeme Russ
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=4EB6E405.4060509@gmail.com \
--to=graeme.russ@gmail.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