From: Corentin Labbe <clabbe@baylibre.com>
To: vgupta@synopsys.com, abrodkin@synopsys.com
Cc: linux-kernel@vger.kernel.org, khilman@baylibre.com,
linux-snps-arc@lists.infradead.org,
Corentin Labbe <clabbe@baylibre.com>
Subject: [PATCH 2/2] arc: hsdk_defconfig: enable CONFIG_ARC_UBOOT_SUPPORT
Date: Tue, 5 Feb 2019 08:32:15 +0000 [thread overview]
Message-ID: <1549355535-22052-3-git-send-email-clabbe@baylibre.com> (raw)
In-Reply-To: <1549355535-22052-1-git-send-email-clabbe@baylibre.com>
We have now a HSDK device in our kernelci lab, but kernel builded via
the hsdk_defconfig ignore bootargs, so it cannot boot kernelci jobs yet.
Furthermore, I think the probability is that devices will be booted more via
uboot than by a debugger.
So this patch enable CONFIG_ARC_UBOOT_SUPPORT in hsdk_defconfig.
Signed-off-by: Corentin Labbe <clabbe@baylibre.com>
---
arch/arc/configs/hsdk_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arc/configs/hsdk_defconfig b/arch/arc/configs/hsdk_defconfig
index 0e5fd29ed238..b80e3ac5c93c 100644
--- a/arch/arc/configs/hsdk_defconfig
+++ b/arch/arc/configs/hsdk_defconfig
@@ -9,6 +9,7 @@ CONFIG_NAMESPACES=y
# CONFIG_PID_NS is not set
CONFIG_BLK_DEV_INITRD=y
CONFIG_BLK_DEV_RAM=y
+CONFIG_ARC_UBOOT_SUPPORT=y
CONFIG_EMBEDDED=y
CONFIG_PERF_EVENTS=y
# CONFIG_VM_EVENT_COUNTERS is not set
--
2.19.2
next prev parent reply other threads:[~2019-02-05 8:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 8:32 [PATCH 0/2] arc: hsdk_defconfig: permit kernelci jobs Corentin Labbe
2019-02-05 8:32 ` [PATCH 1/2] arc: hsdk_defconfig: Enable CONFIG_BLK_DEV_RAM Corentin Labbe
2019-02-05 8:32 ` Corentin Labbe [this message]
2019-02-05 11:42 ` [PATCH 2/2] arc: hsdk_defconfig: enable CONFIG_ARC_UBOOT_SUPPORT Eugeniy Paltsev
2019-02-05 16:42 ` Vineet Gupta
2019-02-05 16:51 ` Alexey Brodkin
2019-02-05 20:14 ` Kevin Hilman
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=1549355535-22052-3-git-send-email-clabbe@baylibre.com \
--to=clabbe@baylibre.com \
--cc=abrodkin@synopsys.com \
--cc=khilman@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=vgupta@synopsys.com \
/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;
as well as URLs for NNTP newsgroup(s).