mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Jan Weitzel <J.Weitzel@phytec.de>
To: Alexander Aring <alex.aring@googlemail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 2/3] commands: move nandtest to testing
Date: Tue, 11 Sep 2012 09:10:57 +0200	[thread overview]
Message-ID: <1347347457.3888.0.camel@lws-weitzel> (raw)
In-Reply-To: <1347341465-2560-2-git-send-email-alex.aring@gmail.com>

Am Dienstag, den 11.09.2012, 07:31 +0200 schrieb Alexander Aring:
> Move nadntest in commands menu.
nandtest

Jan

> Signed-off-by: Alexander Aring <alex.aring@gmail.com>
> ---
>  commands/Kconfig | 16 ++++++++--------
>  1 file changed, 8 insertions(+), 8 deletions(-)
> 
> diff --git a/commands/Kconfig b/commands/Kconfig
> index 8f3a15a..2ee8643 100644
> --- a/commands/Kconfig
> +++ b/commands/Kconfig
> @@ -192,14 +192,6 @@ config CMD_NAND
>  	depends on NAND
>  	prompt "nand"
>  
> -config CMD_NANDTEST
> -	tristate
> -	depends on NAND
> -	depends on PARTITION
> -	depends on NAND_ECC_HW || NAND_ECC_SOFT
> -	select PARTITION_NEED_MTD
> -	prompt "nandtest"
> -
>  config CMD_AUTOMOUNT
>  	tristate
>  	select FS_AUTOMOUNT
> @@ -474,6 +466,14 @@ endmenu
>  
>  menu "testing                       "
>  
> +config CMD_NANDTEST
> +	tristate
> +	depends on NAND
> +	depends on PARTITION
> +	depends on NAND_ECC_HW || NAND_ECC_SOFT
> +	select PARTITION_NEED_MTD
> +	prompt "nandtest"
> +
>  endmenu
>  
>  config CMD_TIMEOUT



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

  reply	other threads:[~2012-09-11  7:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-11  5:31 [PATCH 1/3] commands: add testing menu Alexander Aring
2012-09-11  5:31 ` [PATCH 2/3] commands: move nandtest to testing Alexander Aring
2012-09-11  7:10   ` Jan Weitzel [this message]
2012-09-11  5:31 ` [PATCH 3/3] commands: move memtest " Alexander Aring
2012-09-11  7:46 ` [PATCH 1/3] commands: add testing menu Sascha Hauer

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=1347347457.3888.0.camel@lws-weitzel \
    --to=j.weitzel@phytec.de \
    --cc=alex.aring@googlemail.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