All of lore.kernel.org
 help / color / mirror / Atom feed
From: Holger Brunck <holger.brunck@keymile.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ppc, mgcoge: add DIP switch detection
Date: Thu, 05 May 2011 09:37:09 +0200	[thread overview]
Message-ID: <4DC253A5.6010109@keymile.com> (raw)
In-Reply-To: <20110505072913.2D655D5F849@gemini.denx.de>

Hi,

On 05/05/2011 09:29 AM, Wolfgang Denk wrote:
> Dear Holger Brunck,
> 
> In message <4DC24DEA.7010201@keymile.com> you wrote:
>>
>>> This patch breaks compiling of the  mgcoge2ne  board:
> ...
>> In the already posted patch serie
>> http://lists.denx.de/pipermail/u-boot/2011-May/091976.html
>> the problem is fixed, should I repost the patch
>> powerpc/km82xx: rework DIP switch detection
>> as a standalone patch and rebase the serie or can you take the whole serie?
> 
> 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.

Best regards
Holger Brunck

  reply	other threads:[~2011-05-05  7:37 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 [this message]
2011-05-05 18:16         ` Wolfgang Denk
2011-05-06  8:10           ` Holger Brunck
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=4DC253A5.6010109@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.