All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/7] AT49BV322A Flash: the erase regions are in the wrong order.
Date: Fri, 9 Apr 2010 08:46:17 +0200	[thread overview]
Message-ID: <201004090846.17760.sr@denx.de> (raw)
In-Reply-To: <op.vauotwzjqigx4y@cyprus.local>

Hi David,

On Thursday 08 April 2010 17:47:46 David Wu wrote:
> > I didn't mean that you should split this patch, but that you should
> > split it
> > from your *patchset* of 7 parts. Resulting in a patchset with 6 parts
> > ([PATCH
> > 1/6] ...) and one single patch. This way it's easier for me to pick up
> > such a
> > CFI related patch.
> 
> OK. Will do it.
> A question: Do I have to do this way or just for convenience ?
> My concerns are
> 1 more traffic to the list

Why would there be more traffic? Previously you did send 7 patches, numbered 
1/7 ... 7/7. Now you would send 7 patches 1/6 ... 6/6 plus the CFI patch.

> 2 git will complain if applying the patch in the wrong order.

The CFI patch is unrelated to the other patches. At least it wont generate any 
compilation breakages/problems, if this patch is applied before or after your 
other Coldfire patches.

Cheers,
Stefan

--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: office at denx.de

  reply	other threads:[~2010-04-09  6:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-08  0:00 [U-Boot] [PATCH 2/7] AT49BV322A Flash: the erase regions are in the wrong order David Wu
2010-04-08  9:35 ` Stefan Roese
2010-04-08 15:16   ` David Wu
2010-04-08 15:21     ` Stefan Roese
2010-04-08 15:47       ` David Wu
2010-04-09  6:46         ` Stefan Roese [this message]
2010-04-09 15:11           ` David Wu
2010-04-09 17:05             ` Stefan Roese

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=201004090846.17760.sr@denx.de \
    --to=sr@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 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.