From: Holger Brunck <holger.brunck@keymile.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ppc, mgcoge: add DIP switch detection
Date: Fri, 06 May 2011 10:10:57 +0200 [thread overview]
Message-ID: <4DC3AD11.5080509@keymile.com> (raw)
In-Reply-To: <20110505181654.AD524D60EB7@gemini.denx.de>
On 05/05/2011 08:16 PM, Wolfgang Denk wrote:
> Dear Holger Brunck,
>
> In message <4DC253A5.6010109@keymile.com> you wrote:
>>
>>> As the merge window is closed, this new patch series will not go into
>>> this upcoming release any more.
>>
>> Sorry but why this? The initial patch serie was postet on april 8th:
>> http://lists.denx.de/pipermail/u-boot/2011-April/090012.html
>> And as far as I know the merge window was closed on april 10th.
>>
>> The resulting patch series are a rework due to the input of the ML.
>
> The reworked series goes in, but there appear to be a number of
> completely new patches; these go into next.
>
yes if there is something completely new it goes into next. But both reworked
series posted from myside have no new patches and no new features inside the
patches. Ok two patches are squashed to one, as a result of an input from your
side and I thought this was ok. If you still see something let me know and I
remove it from the serie.
So back to my original question should I post a bugfix patch for the compile
issue for mgcoge2ne and rebase the serie "[PATCH v2 0/7] km82xx mainlining"
above this patch or is it ok if it get fixed with this serie?
Best regards
Holger Brunck
next prev parent reply other threads:[~2011-05-06 8:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 10:26 [U-Boot] [PATCH] ppc, mgcoge: add DIP switch detection Holger Brunck
2011-04-11 20:41 ` Wolfgang Denk
2011-05-04 20:01 ` Wolfgang Denk
2011-05-05 7:12 ` Holger Brunck
2011-05-05 7:29 ` Wolfgang Denk
2011-05-05 7:37 ` Holger Brunck
2011-05-05 18:16 ` Wolfgang Denk
2011-05-06 8:10 ` Holger Brunck [this message]
2011-05-06 10:17 ` Wolfgang Denk
2011-05-06 11:26 ` Holger Brunck
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=4DC3AD11.5080509@keymile.com \
--to=holger.brunck@keymile.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