public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Reinhard Meyer <u-boot@emk-elektronik.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Makes AT91SAM9261-EK build correctly against the mainline HEAD
Date: Sat, 11 Jun 2011 08:17:31 +0200	[thread overview]
Message-ID: <4DF3087B.3070606@emk-elektronik.de> (raw)
In-Reply-To: <1307772069-13120-1-git-send-email-hong.xu@atmel.com>

Dear Hong Xu,
> Rework for AT91SAM9261-EK, makes it build again.
> Based on the work for AT91SAM9260-EK.
>
> Signed-off-by: voice<voice.shen@atmel.com>
> Signed-off-by: Hong Xu<hong.xu@atmel.com>
> ---
>   Makefile                                           |   23 ----
>   arch/arm/cpu/arm926ejs/at91/at91sam9261_devices.c  |   45 +++----
>   arch/arm/include/asm/arch-at91/at91_spi.h          |    2 +-
>   arch/arm/include/asm/arch-at91/at91sam9261.h       |    2 +-
>   .../arm/include/asm/arch-at91/at91sam9261_matrix.h |   77 +++++------
>   board/atmel/at91sam9261ek/at91sam9261ek.c          |  136 ++++++++++---------
>   board/atmel/at91sam9261ek/config.mk                |    1 -
>   board/atmel/at91sam9261ek/led.c                    |    7 +-
>   boards.cfg                                         |    6 +
>   include/configs/at91sam9261ek.h                    |   81 +++++++-----
>   10 files changed, 184 insertions(+), 196 deletions(-)
>   delete mode 100644 board/atmel/at91sam9261ek/config.mk
Could you please make separate patches for the parts that fix the SoC itself,
and for what fixes the board?

I by now have several similar SoC fixes gotten as patches, I have to somehow
make the best of them.... I might have to pick parts from each of them.

Best Regards,
Reinhard

  reply	other threads:[~2011-06-11  6:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-11  6:01 [U-Boot] [PATCH] Makes AT91SAM9261-EK build correctly against the mainline HEAD Hong Xu
2011-06-11  6:17 ` Reinhard Meyer [this message]
2011-06-11  6:23 ` Reinhard Meyer

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=4DF3087B.3070606@emk-elektronik.de \
    --to=u-boot@emk-elektronik.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox