All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Ziswiler <marcel@ziswiler.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH][v2] mpc8260: move FDT memory node fixup into common CPU code.
Date: Tue, 08 Sep 2009 23:51:06 +0200	[thread overview]
Message-ID: <1252446666.5386.102.camel@com-21> (raw)
In-Reply-To: <20090908211930.1E493832E8DE@gemini.denx.de>

On Tue, 2009-09-08 at 23:19 +0200, Wolfgang Denk wrote:
> No, on contrary. New versions of a patch should always make sure to
> thread correctly to the old version(s). It seems that preferences here
> are a matter of taste - my personal preference is to link to the
> preceeding version of the patch, but most others seem to prefer to
> link to the first version always.

That's kind of what I thought at first as well, but then I saw many
others posting patches not adhering to that and still getting your ack
no problem:
http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/67581
http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/67462
http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/67394
http://article.gmane.org/gmane.comp.boot-loaders.u-boot/67187

  reply	other threads:[~2009-09-08 21:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-08 15:32 [U-Boot] [PATCH][v2] mpc8260: move FDT memory node fixup into common CPU code Marcel Ziswiler
2009-09-08 18:25 ` Wolfgang Denk
2009-09-08 20:10   ` Marcel Ziswiler
2009-09-08 20:44     ` Wolfgang Denk
2009-09-08 21:02       ` Marcel Ziswiler
2009-09-08 21:19         ` Wolfgang Denk
2009-09-08 21:51           ` Marcel Ziswiler [this message]
2009-09-09  6:35 ` Heiko Schocher
2009-09-09 19:20 ` [U-Boot] [PATCH][v3] " Marcel Ziswiler
2009-09-10 21:08   ` Wolfgang Denk
2009-10-01 21:55     ` [U-Boot] [PATCH][v4] " Marcel Ziswiler
2009-11-22 22:16       ` Wolfgang Denk

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=1252446666.5386.102.camel@com-21 \
    --to=marcel@ziswiler.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.