public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Yegor Yefremov <yegor_sub1@visionsystems.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] am3517evm: remove rootfstype kernel parameter for MMC boot device
Date: Wed, 25 Jan 2012 09:06:50 +0100	[thread overview]
Message-ID: <4F1FB81A.4030509@visionsystems.de> (raw)
In-Reply-To: <4E243A4E.9070904@visionsystems.de>

Am 18.07.2011 15:51, schrieb Yegor Yefremov:
> From 53afd3a38abbaed8890ca1ba36439e0c93b69969 Mon Sep 17 00:00:00 2001
> From: Yegor Yefremov <yegorslists@googlemail.com>
> Date: Mon, 18 Jul 2011 15:44:42 +0200
> Subject: [PATCH] am3517evm: remove rootfstype kernel parameter for MMC boot device
> 
> it is not necessary to define rootfstype for mass storage devices.
> Kernel detects it automatically.
> 
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
> ---
>  include/configs/am3517_evm.h |    3 +--
>  1 files changed, 1 insertions(+), 2 deletions(-)
> 
> diff --git a/include/configs/am3517_evm.h b/include/configs/am3517_evm.h
> index 18aaadf..8b8c80b 100644
> --- a/include/configs/am3517_evm.h
> +++ b/include/configs/am3517_evm.h
> @@ -192,8 +192,7 @@
>  	"loadaddr=0x82000000\0" \
>  	"console=ttyO2,115200n8\0" \
>  	"mmcargs=setenv bootargs console=${console} " \
> -		"root=/dev/mmcblk0p2 rw " \
> -		"rootfstype=ext3 rootwait\0" \
> +		"root=/dev/mmcblk0p2 rw rootwait\0" \
>  	"nandargs=setenv bootargs console=${console} " \
>  		"root=/dev/mtdblock4 rw " \
>  		"rootfstype=jffs2\0" \

Could you please review this patch? It is very annoying when using Buildroot as it creates ext2 images.

Thanks.

Yegor 

  reply	other threads:[~2012-01-25  8:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-18 13:51 [U-Boot] [PATCH] am3517evm: remove rootfstype kernel parameter for MMC boot device Yegor Yefremov
2012-01-25  8:06 ` Yegor Yefremov [this message]
2012-01-25 21:31   ` Tom Rini

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=4F1FB81A.4030509@visionsystems.de \
    --to=yegor_sub1@visionsystems.de \
    --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