All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Stefano Stabellini <sstabellini@kernel.org>,
	Doug Goldstein <cardoe@cardoe.com>,
	"fam@euphon.net" <fam@euphon.net>, <Bertrand.Marquis@arm.com>,
	<famzheng@amazon.com>, <wl@xen.org>, <julien@xen.org>,
	<jbeulich@suse.com>
Cc: <xen-devel@lists.xenproject.org>
Subject: Re: more randconfig failures
Date: Wed, 27 Jan 2021 21:23:48 +0000	[thread overview]
Message-ID: <45a1b4b2-afd7-9b70-e857-d0c23f2fd26e@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2101271311470.9684@sstabellini-ThinkPad-T480s>

On 27/01/2021 21:16, Stefano Stabellini wrote:
> Hi all,
>
> These are two recent randconfig build failures reported by gitlab (the
> two patches that triggered the CI-loop are two patches to the
> MAINTAINERS file -- certainly not the cause of the build issues):
>
> x86 randconfig failure:
> https://gitlab.com/xen-project/patchew/xen/-/jobs/990347647

This has been known and a source of intermittent failures for ages.

I already laid out how to fix it, by removing some inappropriate Kconfig
dependencies.  I'll get around to writing some patches when there aren't
more important tasks to do for 4.15.

~Andrew


  reply	other threads:[~2021-01-27 21:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-27 21:16 more randconfig failures Stefano Stabellini
2021-01-27 21:23 ` Andrew Cooper [this message]
2021-01-28  8:11   ` Jan Beulich
2021-01-27 21:25 ` Julien Grall
2021-01-27 23:11   ` Rahul Singh
2021-01-28 16:34     ` Julien Grall
2021-01-28 16:46       ` Jan Beulich
2021-01-28 17:45         ` Julien Grall
2021-01-28 17:20       ` Rahul Singh

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=45a1b4b2-afd7-9b70-e857-d0c23f2fd26e@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=Bertrand.Marquis@arm.com \
    --cc=cardoe@cardoe.com \
    --cc=fam@euphon.net \
    --cc=famzheng@amazon.com \
    --cc=jbeulich@suse.com \
    --cc=julien@xen.org \
    --cc=sstabellini@kernel.org \
    --cc=wl@xen.org \
    --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.