All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] ARM next Pull Request
Date: Sun, 24 May 2009 22:36:47 +0200	[thread overview]
Message-ID: <20090524203647.93B77832E416@gemini.denx.de> (raw)
In-Reply-To: <20090524195202.GA29662@game.jcrosoft.org>

Dear Jean-Christophe PLAGNIOL-VILLARD,

In message <20090524195202.GA29662@game.jcrosoft.org> you wrote:
> On 19:42 Sun 24 May     , Wolfgang Denk wrote:
> > Dear Jean-Christophe PLAGNIOL-VILLARD,
> > 
> > In message <20090522230704.GB19891@game.jcrosoft.org> you wrote:
> > > 
> > > Please pull
> > > The following changes since commit cab6c2a6135cc8f4244d8e9c005bddd208d2a26f:
> > >   Wolfgang Denk (1):
> > >         TQM834x: use buffered writes to accelerate writing to flash
> > > 
> > > are available in the git repository at:
> > > 
> > >   git://git.denx.de/u-boot-arm.git next
> > 
> > I'm trying to review your patches, but:
> > 
> > > Jean-Christophe PLAGNIOL-VILLARD (11):
> > >       afeb9260: fix macb device init
> > 
> > ??? This patch has never been posted on the ML before.
> yes just after the precedent pull request

No, I don't see it in the mailing list archives.

> > For this patch, neither the patch itself nor a URL which I can use to
> > download the patch using "wget" or "ftp" or similar has ever been
> > posted.
> it's was more than 2 weeks ago
> http://git.denx.de/?p=u-boot/u-boot-arm.git;a=commitdiff_plain;h=af9c0dff8877bca20a797234078b11c277f04c9d;hp=6df0610e020ea13b2177d732033d5b6b819ec6ed

Thanks. Nevertheless, that's not a patch created by git-format-patch,
and I don't have the usual stat lines that show me immediately the
amount of changes and which files are affected and all that. Please
play by the rules like we request from anybody else.

And can you please try and use complete words in the commit messages
instead of home-made abbreviations? The phrase "use the same cpu lds"
may make sense to you, but do not make much sense to me. I have no
idea what a "cpu lds" is.  Also s/overwrite/overwritten/.


Hmmm... and where is this "patch" supposed to be applied? arm-next"
cannot be used as it's already in there.



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
"The net result is a system that is not only binary  compatible  with
4.3  BSD, but is even bug for bug compatible in almost all features."
- Avadit  Tevanian,  Jr.,  "Architecture-Independent  Virtual  Memory
Management  for  Parallel  and  Distributed  Environments:  The  Mach
Approach"

  reply	other threads:[~2009-05-24 20:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-22 23:07 [U-Boot] ARM next Pull Request Jean-Christophe PLAGNIOL-VILLARD
2009-05-22 23:42 ` Wolfgang Denk
2009-05-24 17:42 ` Wolfgang Denk
2009-05-24 18:07   ` Dirk Behme
2009-05-24 19:52   ` Jean-Christophe PLAGNIOL-VILLARD
2009-05-24 20:36     ` Wolfgang Denk [this message]
2009-05-24 21:22       ` Jean-Christophe PLAGNIOL-VILLARD
2009-05-25  7:27         ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2009-06-03 19:08 Jean-Christophe PLAGNIOL-VILLARD
2009-06-03 20:45 ` Wolfgang Denk
2009-06-03 20:41   ` Jean-Christophe PLAGNIOL-VILLARD
2009-06-03 21:14     ` 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=20090524203647.93B77832E416@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 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.