All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH 4/5] AT91CAP9 support : board/ files
Date: Sun, 3 Feb 2008 21:58:41 +0100	[thread overview]
Message-ID: <20080203205840.GA32030@game.jcrosoft.org> (raw)
In-Reply-To: <20080203135435.46004d53@siona>

On 13:54 Sun 03 Feb     , Haavard Skinnemoen wrote:
> On Sat, 02 Feb 2008 22:25:54 +0100
> Stelian Pop <stelian@popies.net> wrote:
> 
> > Le samedi 02 f?vrier 2008 ? 06:59 +0100, Stefan Roese a ?crit :
> > 
> > > > I did think of that. I have no strong feeling about that. Except that if
> > > > we put at91cap9adk under board/atmel, at91rm9200dk should go there too.  
> > > 
> > > Right. I always prefer to "collect" board ports from one manufacturer/brand 
> > > into a specific directory.  
> > 
> > Manufacturer or brand/type ? Meaning, what do we do with the other AT91
> > based boards, which are not made by Atmel (cmc_pu2, csb637, kb9202,
> > mp2usb) ?
> 
> I think they should be collected according to board manufacturer or
> brand, not cpu type. So boards/atmel is for boards manufactured by
> Atmel, not all boards that happen to have an Atmel cpu on them.

I agree too, they should be collected according to board manufacturer
not cpu type.

Best Regards,
J.

  reply	other threads:[~2008-02-03 20:58 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-31 21:15 [U-Boot-Users] [PATCH ARM 0/5] AT91CAP9 support Stelian Pop
2008-01-31 21:15 ` [U-Boot-Users] [PATCH 1/5] AT91CAP9 support : build integration Stelian Pop
2008-01-31 21:15 ` [U-Boot-Users] [PATCH 2/5] AT91CAP9 support : include/ files Stelian Pop
2008-01-31 21:15 ` [U-Boot-Users] [PATCH 3/5] AT91CAP9 support : cpu/ files Stelian Pop
2008-01-31 23:24   ` Ulf Samuelsson
2008-02-01 20:48     ` Stelian Pop
2008-01-31 21:15 ` [U-Boot-Users] [PATCH 4/5] AT91CAP9 support : board/ files Stelian Pop
2008-01-31 22:59   ` Ulf Samuelsson
2008-02-01 20:52     ` Stelian Pop
2008-02-02  5:59       ` Stefan Roese
2008-02-02 21:25         ` Stelian Pop
2008-02-03  6:44           ` Ulf Samuelsson
2008-02-03 15:49             ` Wolfgang Denk
2008-02-03 12:54           ` Haavard Skinnemoen
2008-02-03 20:58             ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2008-02-04  9:42             ` [U-Boot-Users] [PATCH ARM] AT91CAP9 support : move board files to Atmel vendor directory Stelian Pop
2008-02-04  9:54               ` Stefan Roese
2008-02-04 10:26               ` [U-Boot-Users] [PATCH ARM] AT91CAP9 support : move board files to Atmel vendordirectory Peter Pearse
2008-02-02 11:40       ` [U-Boot-Users] [PATCH] Move AT91RM9200DK board support under board/atmel Haavard Skinnemoen
2008-02-02 12:37         ` Haavard Skinnemoen
2008-02-14 14:20           ` Peter Pearse
2008-02-02 12:47         ` Stefan Roese
2008-01-31 21:15 ` [U-Boot-Users] [PATCH 5/5] AT91CAP9 support : MACB changes Stelian Pop
  -- strict thread matches above, loose matches on Subject: below --
2008-01-29 19:49 [U-Boot-Users] [PATCH ARM 0/5] AT91CAP9 support Stelian Pop
2008-01-29 19:49 ` [U-Boot-Users] [PATCH 4/5] AT91CAP9 support : board/ files Stelian Pop
2008-01-31  7:28   ` Jean-Christophe PLAGNIOL-VILLARD
2008-01-31 10:13   ` Ladislav Michl
2008-01-31 21:20     ` Stelian Pop

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=20080203205840.GA32030@game.jcrosoft.org \
    --to=plagnioj@jcrosoft.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.