public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Add support for the KwikByte KBOC OMAP35xx board
Date: Sun, 12 Jul 2009 17:06:02 +0200	[thread overview]
Message-ID: <4A59FBDA.70004@googlemail.com> (raw)
In-Reply-To: <20090712144830.1C393832E416@gemini.denx.de>

Dear Wolfgang,

Wolfgang Denk wrote:
> Dear Dirk Behme,
> 
> In message <4A59E6B3.1070501@googlemail.com> you wrote:
>> Jean-Christophe PLAGNIOL-VILLARD wrote:
>>>>> diff --git a/board/omap3/kboc/kboc.h b/board/omap3/kboc/kboc.h
>>> please create you own vendor dirent
>> NACK. We use board/omap3/<board>/<board>.h syntax. So this is fine. 
>> Everything else would make it inconsistent.
> 
> I'm not sure what you mean by "we" here. 

Most probably the maintainers of all existing board/omap3/* and 
board/davinci/* boards ;)

> The rus  is  that  a  vendor
> directory  shall  be  used  when  a company supports any significaant
> number (say, more than 2...3) of boards. So when for example  company
> FOO who already have other boards in board/foo/* releases their first
> OMAP3 board, it will naturally go into board/foo/

Yes, ok, fine.

I understood Jean-Christophe that he wants

board/omap3/<vendor>

and this is what I doesn't like. At least not for the first board of a 
company. If they, later, add some additional (OMAP3) boards, moving 
then to board/omap3/<vendor>/<board_A>/, 
board/omap3/<vendor>/<board_B>/ etc would be fine, though. But please 
don't make the currently used schema inconsistent just for one (the 
first) board (not knowing if there ever will be an additional one).

Best regards

Dirk

  reply	other threads:[~2009-07-12 15:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-09 23:03 [U-Boot] [PATCH] Add support for the KwikByte KBOC OMAP35xx board christian at kwikbyte.com
2009-07-10  1:06 ` Nishanth Menon
2009-07-10 16:27   ` christian at kwikbyte.com
2009-07-12 13:13   ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-12 13:35     ` Dirk Behme
2009-07-12 14:48       ` Wolfgang Denk
2009-07-12 15:06         ` Dirk Behme [this message]
2009-07-12 15:52           ` Wolfgang Denk
2009-07-12 15:20       ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-12 15:34         ` Dirk Behme
2009-07-12 14:25     ` Nishanth Menon
2009-07-12 14:31       ` Dirk Behme
2009-07-12 14:50         ` [U-Boot] OMAP MUX handling improvement (was: Add support for the KwikByte KBOC OMAP35xx board) Nishanth Menon
2009-07-12 15:28           ` [U-Boot] OMAP MUX handling improvement Dirk Behme
2009-07-12 14:45     ` [U-Boot] [PATCH] Add support for the KwikByte KBOC OMAP35xx board Wolfgang Denk

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=4A59FBDA.70004@googlemail.com \
    --to=dirk.behme@googlemail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox