From: Sascha Hauer <s.hauer@pengutronix.de>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: barebox <barebox@lists.infradead.org>
Subject: Re: [RFC] reference errors in OMAP documetation
Date: Wed, 24 Aug 2011 18:32:13 +0200 [thread overview]
Message-ID: <20110824163213.GI31404@pengutronix.de> (raw)
In-Reply-To: <CAA4bVAFi6B9fsNYn8KLor0_ObZVc2GmxXtwpeuaAC1N7Vt9H+Q@mail.gmail.com>
On Tue, Aug 23, 2011 at 06:40:24PM +0400, Antony Pavlov wrote:
> Hi!
>
> I posted this message some times ago, but nobody commented it.
> So I reposting it.
>
>
> I found some file reference errors in OMAP documentation.
>
> I have made the patch, but I can't send it via git-send-email:
> some lines in dox file are too long.
>
> Here is the patch, please look at it:
>
> http://prizma.bmstu.ru/~antony/barebox/0001-ARM-fix-formatting-and-file-references-in-documentat.patch
I just added a wiki account for you, let me know if this works.
We could add a developer/arm/omap page in the wiki with the correct
version of the text. There are some parts in it I don't exactly agree
with, for example the policy to put all omap boards into
arch/arm/boards/omap. The panda board does not do so and really the
other boards shouldn't do it aswell.
Originally Nishanth said that all omap boards are so similar that
the code should be in a single directory. I did not realize it
at that time, having common code is a good thing, but it should go
to arch/arm/mach-omap and the board code still in arch/arm/boards/<name>
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2011-08-24 16:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-23 14:40 Antony Pavlov
2011-08-24 16:32 ` Sascha Hauer [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=20110824163213.GI31404@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=antonynpavlov@gmail.com \
--cc=barebox@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