All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PULL] U-Boot PXA
Date: Sun, 28 Aug 2011 20:49:02 +0200	[thread overview]
Message-ID: <201108282049.02428.marek.vasut@gmail.com> (raw)
In-Reply-To: <20110828102034.50308166C8CB@gemini.denx.de>

On Sunday, August 28, 2011 12:20:34 PM Wolfgang Denk wrote:
> Dear Marek Vasut,
> 
> In message <201108280639.56242.marek.vasut@gmail.com> you wrote:
> > I prepared a branch for you to pull containing PXA fixes:
> > 
> > Cheers
> > 
> > The following changes since commit 6e8a3951f7656958cefccab55945604a8bbc43e7:
> >   Merge branch 'master' of git://git.denx.de/u-boot (2011-08-28 01:36:27
> >   +0200)
> > 
> > are available in the git repository at:
> >   git://git.denx.de/u-boot-pxa.git for-arm-fix
> > 
> > Marek Vasut (3):
> >       PXA: Fix Lubbock, remove redundant parenthesis
> >       PXA: Fix CSB226, fix monitor length
> >       PXA: vpac270: Remove re-defined CONFIG_SYS_TEXT_BASE
> 
> Again, what a mess... Why are you selecting just 3 commits from a 6
> patches series?  This makes no sense.
> 
Because Albert wanted me to send a pull rq with the PXA fixes. I don't know if he 
hand-picked them already or not, but if not, here's a pull request.

> 
> Either these are separate, independent patches, then submit
> separately.  Or they form a series, with patches depending on each
> other, then obviously you want to include ALL of them? Ok, # 3 and 4
> are for other custodians, but there is still # 6 missing here?
> 
> Best regards,
> 
> Wolfgang Denk

Cheers!

  reply	other threads:[~2011-08-28 18:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-28  4:39 [U-Boot] [PULL] U-Boot PXA Marek Vasut
2011-08-28 10:20 ` Wolfgang Denk
2011-08-28 18:49   ` Marek Vasut [this message]
2011-08-28 20:55     ` Wolfgang Denk
2011-08-28 21:53       ` Marek Vasut

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=201108282049.02428.marek.vasut@gmail.com \
    --to=marek.vasut@gmail.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.