From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ppc, mgcoge: add DIP switch detection
Date: Fri, 06 May 2011 12:17:16 +0200 [thread overview]
Message-ID: <20110506101716.D80C7D60EB7@gemini.denx.de> (raw)
In-Reply-To: <4DC3AD11.5080509@keymile.com>
Dear Holger Brunck,
In message <4DC3AD11.5080509@keymile.com> you wrote:
>
> 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.
OK.
> 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?
If it's not too much of effort, I'd appreciate a separate bug fix,
which I can pull without longer review. Thanks!
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Heavier than air flying machines are impossible.
-- Lord Kelvin, President, Royal Society, c. 1895
next prev parent reply other threads:[~2011-05-06 10:17 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
2011-05-06 10:17 ` Wolfgang Denk [this message]
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=20110506101716.D80C7D60EB7@gemini.denx.de \
--to=wd@denx.de \
--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