From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 6/6] rockchip: Drop old CONFIG_VIDEO_ROTATION option
Date: Sat, 6 Feb 2016 14:18:27 +0100 [thread overview]
Message-ID: <20160206141827.3faac780@crub> (raw)
In-Reply-To: <1454193919-27264-6-git-send-email-sjg@chromium.org>
On Sat, 30 Jan 2016 15:45:19 -0700
Simon Glass sjg at chromium.org wrote:
> The option was renamed to CONFIG_CONSOLE_ROTATION and Rockchip boards
> were not updated. However this option is is not needed by default for
> Rockchip since we don't need a rotated console for current boards. So just
> remove the old option.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
> ---
>
> configs/chromebook_jerry_defconfig | 1 -
> configs/firefly-rk3288_defconfig | 1 -
> configs/rock2_defconfig | 1 -
> 3 files changed, 3 deletions(-)
applied to u-boot-staging, thanks!
--
Anatolij
next prev parent reply other threads:[~2016-02-06 13:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-30 22:45 [U-Boot] [PATCH 1/6] microblaze: Correct build error in eth-uclass.c Simon Glass
2016-01-30 22:45 ` [U-Boot] [PATCH 2/6] cmd: Fix control bmp_display() Simon Glass
2016-02-01 16:54 ` Tom Rini
2016-02-06 13:04 ` Anatolij Gustschin
2016-01-30 22:45 ` [U-Boot] [PATCH 3/6] video: Use 'int' for loop variables instead of short Simon Glass
2016-02-01 16:54 ` Tom Rini
2016-02-06 13:05 ` Anatolij Gustschin
2016-01-30 22:45 ` [U-Boot] [PATCH 4/6] video: test: Adjust order of file closure Simon Glass
2016-02-01 16:54 ` Tom Rini
2016-02-06 13:06 ` Anatolij Gustschin
2016-01-30 22:45 ` [U-Boot] [PATCH 5/6] bzlib: Try another way to fix an unused variable Simon Glass
2016-02-01 16:54 ` Tom Rini
2016-02-06 13:12 ` Anatolij Gustschin
2016-01-30 22:45 ` [U-Boot] [PATCH 6/6] rockchip: Drop old CONFIG_VIDEO_ROTATION option Simon Glass
2016-02-01 16:55 ` Tom Rini
2016-02-06 13:18 ` Anatolij Gustschin [this message]
2016-02-01 16:52 ` [U-Boot] [PATCH 1/6] microblaze: Correct build error in eth-uclass.c Joe Hershberger
2016-02-06 13:03 ` Anatolij Gustschin
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=20160206141827.3faac780@crub \
--to=agust@denx.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