Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] [patch] AVR32: rename atstk1002 target board	to	more generic	atstk100x
Date: Thu, 24 Apr 2008 12:38:57 +0200	[thread overview]
Message-ID: <1209033537.18722.5.camel@localhost> (raw)
In-Reply-To: <1208348434.8069.5.camel@localhost>

Bump

Any chance of getting this through?

On Wed, 2008-04-16 at 14:20 +0200, Hans-Christian Egtvedt wrote:
> On Wed, 2008-04-16 at 10:52 +0200, Hans-Christian Egtvedt wrote:
> > Hi,
> > 
> > Please consider applying the linked patch:
> > 
> > http://www.atmel.no/~hcegtvedt/patches/0001-AVR32-rename-atstk1002-target-board-to-more-generic.patch
> > 
> 
> Hmmm, nah, git format-patch did not do the trick for patch.
> 
> The patch below will work, but requires some manual hands-on.
> 
> http://www.atmel.no/~hcegtvedt/patches/0001-AVR32-rename-atstk1002-target-board-to-more-generic-take2.patch
> 
> patch -p1 < 0001-AVR32-rename-atstk1002-target-board-to-more-generic-take2.patch
> ~ > mv target/device/Atmel/atstk1002/* target/device/Atmel/atstk100x/
> ~ > rmdir target/device/Atmel/atstk1002
> 
> Then commit.
> 
> I update the two _defconfigs to reflect the changes.
> 
> > This patch renames the Atmel atstk1002 target board to a more generic
> > atstk100x name. This to make it easier to add support for other
> > CPU-boards than atstk1002.
> > 
> > Signed-off-by: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
> > 
> > Applies clean to snapshot from 20080416.
> > 
> 
> Should apply clean now.
> 
-- 
With kind regards,
Hans-Christian Egtvedt, Applications Engineer

      reply	other threads:[~2008-04-24 10:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-16  8:52 [Buildroot] [patch] AVR32: rename atstk1002 target board to more generic atstk100x Hans-Christian Egtvedt
2008-04-16 12:20 ` Hans-Christian Egtvedt
2008-04-24 10:38   ` Hans-Christian Egtvedt [this message]

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=1209033537.18722.5.camel@localhost \
    --to=hans-christian.egtvedt@atmel.com \
    --cc=buildroot@busybox.net \
    /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