Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] ARM: Basic Xilinx Support
Date: Sat, 5 Feb 2011 16:47:00 +0000	[thread overview]
Message-ID: <20110205164700.GF29411@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <eab51420-2be9-429a-8c59-76b3206bc15e@VA3EHSMHS033.ehs.local>

On Sat, Feb 05, 2011 at 09:08:40AM -0700, John Linn wrote:
> This patch series adds very basic support for the Xilinx ARM platform.
> The entire patch set must be used. I only broke it up into logical 
> pieces to make the review easier (I hope). 

It's actually a question of patch ordering - if patch 1 comes at the
end, the other patches are just putting the files in place.  Until
patch 1 is in place, none of it will be built.

If it's necessary to split stuff in this manner, it's quite usual for
the configuration/makefile additions to come last in the series to
avoid build errors half way through.

  reply	other threads:[~2011-02-05 16:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-05 16:08 [PATCH 0/4] ARM: Basic Xilinx Support John Linn
2011-02-05 16:47 ` Russell King - ARM Linux [this message]
2011-02-05 16:49   ` John Linn

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=20110205164700.GF29411@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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