mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Juergen Beisert <jbe@pengutronix.de>
To: barebox@lists.infradead.org
Subject: Re: [PATCH 13/32] doc: fix typo
Date: Fri, 22 Oct 2010 19:21:31 +0200	[thread overview]
Message-ID: <201010221921.31210.jbe@pengutronix.de> (raw)
In-Reply-To: <1287765924-1856-14-git-send-email-r.schwebel@pengutronix.de>

Robert Schwebel wrote:
> Remove a # which leads to this warning:
> arch/arm/mach-s3c24xx/lowlevel-init.S:307: Warning: explicit link request
> to 'CALC_NFCONF_TIMING' could not be resolved
>
> Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
> ---
>  arch/arm/mach-s3c24xx/lowlevel-init.S |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm/mach-s3c24xx/lowlevel-init.S
> b/arch/arm/mach-s3c24xx/lowlevel-init.S index e8004e5..27f3a32 100644
> --- a/arch/arm/mach-s3c24xx/lowlevel-init.S
> +++ b/arch/arm/mach-s3c24xx/lowlevel-init.S
> @@ -304,7 +304,7 @@ minimalistic. Setup the NAND access timing is done in a
> safe manner, what means: Slowest possible values are used. If you want to
> increase the speed you should define the BOARD_DEFAULT_NAND_TIMING to a
> valid setting into the NFCONF register and add it to your board specific
> config.h. Refer S3C24x0's -datasheet for further details. The macro
> #CALC_NFCONF_TIMING could help to +datasheet for further details. The macro
> CALC_NFCONF_TIMING could help to calculate the register setting in a
> hardware independent manner.
>
>  @note The regular NAND driver uses a platform data structure to define the

Hmm, but this macro exists and doxygen should generate a reference to it. 
Don't know why it spits out a warning here.

jbe

-- 
Pengutronix e.K.                              | Juergen Beisert             |
Linux Solutions for Science and Industry      | Phone: +49-8766-939 228     |
Vertretung Sued/Muenchen, Germany             | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686              | http://www.pengutronix.de/  |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2010-10-22 17:21 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-22 16:44 Documentation Updates Robert Schwebel
2010-10-22 16:44 ` [PATCH 01/32] reset_cpu: unify declaration Robert Schwebel
2010-10-22 16:44 ` [PATCH 02/32] Doxyfile: enable quiet output Robert Schwebel
2010-10-22 16:44 ` [PATCH 03/32] Doxyfile: remove obsolete boards directory Robert Schwebel
2010-10-22 16:44 ` [PATCH 04/32] Doxyfile: add exclude rules Robert Schwebel
2010-10-22 16:44 ` [PATCH 05/32] Doxyfile: remove non-existing directories Robert Schwebel
2010-10-22 16:44 ` [PATCH 06/32] Doxyfile: remove unused features Robert Schwebel
2010-10-22 16:44 ` [PATCH 07/32] Doxyfile: enable assembler files Robert Schwebel
2010-10-22 16:45 ` [PATCH 08/32] doc: let doxygen find some assembler functions Robert Schwebel
2010-10-22 16:45 ` [PATCH 09/32] doc: remove nonexisting command Robert Schwebel
2010-10-22 16:45 ` [PATCH 10/32] doc: remove reference to non-existing documentation Robert Schwebel
2010-10-22 16:45 ` [PATCH 11/32] doc: eliminate nonexisting reference Robert Schwebel
2010-10-22 16:45 ` [PATCH 12/32] doc: add missing quoting Robert Schwebel
2010-10-22 16:45 ` [PATCH 13/32] doc: fix typo Robert Schwebel
2010-10-22 17:21   ` Juergen Beisert [this message]
2010-10-22 16:45 ` [PATCH 14/32] doc: mark code explicitely Robert Schwebel
2010-10-22 16:45 ` [PATCH 15/32] doc: avoid that doxygen parses magic in command.h Robert Schwebel
2010-10-22 16:45 ` [PATCH 16/32] doc: fix wrongly named parameter Robert Schwebel
2010-10-22 16:45 ` [PATCH 17/32] doc: fix parameter name in mci-core Robert Schwebel
2010-10-22 16:45 ` [PATCH 18/32] doc: silence doxygen warnings Robert Schwebel
2010-10-22 18:50   ` Sascha Hauer
2010-10-22 16:45 ` [PATCH 19/32] doc: add macros to unify command help with doxygen Robert Schwebel
2010-10-22 16:45 ` [PATCH 20/32] doc: add documentation for 'bmp' Robert Schwebel
2010-10-22 16:45 ` [PATCH 21/32] doc: add documentation for 'clear' Robert Schwebel
2010-10-22 16:45 ` [PATCH 22/32] doc: add documentation for 'crc32' Robert Schwebel
2010-10-22 16:45 ` [PATCH 23/32] doc: add documentation for 'dfu' Robert Schwebel
2010-10-22 16:45 ` [PATCH 24/32] doc: unify documentation for 'ls' Robert Schwebel
2010-10-22 16:45 ` [PATCH 25/32] doc: unify documentation for 'cat' Robert Schwebel
2010-10-22 16:45 ` [PATCH 26/32] doc: unify documentation for 'cd' Robert Schwebel
2010-10-22 16:45 ` [PATCH 27/32] doc: add documentation for 'echo' Robert Schwebel
2010-10-22 16:45 ` [PATCH 28/32] doc: unify documentation for 'edit' Robert Schwebel
2010-10-22 16:45 ` [PATCH 29/32] doc: add documentation for 'bootm' Robert Schwebel
2010-10-22 16:45 ` [PATCH 30/32] doc: unify documentation for 'addpart' Robert Schwebel
2010-10-22 16:45 ` [PATCH 31/32] doc: unify documentation for 'cp' Robert Schwebel
2010-10-22 16:45 ` [PATCH 32/32] doc: unify documentation for 'delpart' Robert Schwebel

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=201010221921.31210.jbe@pengutronix.de \
    --to=jbe@pengutronix.de \
    --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