All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Jackson <ian.jackson@eu.citrix.com>
To: <xen-devel@lists.xenproject.org>
Cc: Julien Grall <julien.grall@arm.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>
Subject: [Xen-devel] [OSSTEST PATCH 4/4] ts-kernel-build: Actually disable CONFIG_ARCH_QCOM
Date: Tue, 24 Sep 2019 15:42:44 +0100	[thread overview]
Message-ID: <20190924144244.7940-4-ian.jackson@eu.citrix.com> (raw)
In-Reply-To: <20190924144244.7940-1-ian.jackson@eu.citrix.com>

osstest c/s efeddf7eca86
  ts-kernel-build: Disable CONFIG_ARCH_QCOM in Xen Project CI
did not work because it lacked the needed `setopt'.  Oops.

CC: Julien Grall <julien.grall@arm.com>
Suggested-by: Julien Grall <julien.grall@arm.com>
Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
---
 ts-kernel-build | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/ts-kernel-build b/ts-kernel-build
index 56ff7994..c976289e 100755
--- a/ts-kernel-build
+++ b/ts-kernel-build
@@ -276,7 +276,7 @@ setopt CONFIG_SPI_THUNDERX=m
 
 # Some Linux branches we care about, including 4.19, still lack
 # firmware: qcom_scm: Use proper types for dma mappings
-CONFIG_ARCH_QCOM=n
+setopt CONFIG_ARCH_QCOM=n
 
 ####
 
-- 
2.11.0


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

      parent reply	other threads:[~2019-09-24 14:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-24 14:42 [Xen-devel] [OSSTEST PATCH 1/4] TestSupport: Break out target_getfile_something_stash Ian Jackson
2019-09-24 14:42 ` [Xen-devel] [OSSTEST PATCH 2/4] TestSupport: Provide target_getfile_stash Ian Jackson
2019-09-24 14:42 ` [Xen-devel] [OSSTEST PATCH 3/4] ts-*-build: Save the .config (as <host>--kconfig) Ian Jackson
2019-09-24 14:42 ` Ian Jackson [this message]

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=20190924144244.7940-4-ian.jackson@eu.citrix.com \
    --to=ian.jackson@eu.citrix.com \
    --cc=julien.grall@arm.com \
    --cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.