From: Ingo Molnar <mingo@kernel.org>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: "Juergen Gross" <jgross@suse.com>,
xen-devel@lists.xenproject.org, kvm@vger.kernel.org,
"Radim Krčmář" <rkrcmar@redhat.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
"Ingo Molnar" <mingo@redhat.com>,
"David Vrabel" <david.vrabel@citrix.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Boris Ostrovsky" <boris.ostrovsky@oracle.com>,
"Arjan van de Ven" <arjan@linux.intel.com>,
"Thomas Gleixner" <tglx@linutronix.de>
Subject: Re: [PATCH 0/8] x86: audit and remove needless module.h includes
Date: Thu, 14 Jul 2016 20:56:21 +0200 [thread overview]
Message-ID: <20160714185621.GA21092__31409.0663604022$1468522668$gmane$org@gmail.com> (raw)
In-Reply-To: <20160714184603.GR4194@windriver.com>
* Paul Gortmaker <paul.gortmaker@windriver.com> wrote:
> [Re: [PATCH 0/8] x86: audit and remove needless module.h includes] On 14/07/2016 (Thu 20:39) Ingo Molnar wrote:
>
> >
> > * Paul Gortmaker <paul.gortmaker@windriver.com> wrote:
> >
> > > > I'll continue testing with the setup_percpu.c change left out.
> > >
> > > Let me know if you want a resend or if you want to just add the
> > > asm/desc.h locally or ...
> >
> > So I tried the asm/desc.h but saw other build failures - for now gave up.
> > Can we do this in a separate patch?
>
> Yes of course. In the meantime I'll investigate further and add more
> configs to my testing. Is there a list of the configs used for sanity
> testing tip somewhere?
No need for you to complicate your testing (unless you have enough hardware
resources for that) - I can deal with the occasional build failure. Since I
eventually create and boot randconfigs there's no fixed set of configs. :-/
That I enabled SMP on the "allnoconfig" (and forgot about it!) has to do with the
fact that even my allnoconfigs are typically bootable (on one of my test systems)
so there's a handful of pre-baked configs that always get enabled.
But other than those small perturbations I do similar testing to what you did:
all{no|def|mod|yes}config on x86-{32|64}, plus randconfigs.
Thanks,
Ingo
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-07-14 18:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160714001901.31603-1-paul.gortmaker@windriver.com>
2016-07-14 0:18 ` [PATCH 6/8] x86: xen: audit and remove any unnecessary uses of module.h Paul Gortmaker
2016-07-14 3:59 ` Juergen Gross
2016-07-14 13:04 ` [PATCH 0/8] x86: audit and remove needless module.h includes Ingo Molnar
[not found] ` <20160714130443.GA27637@gmail.com>
2016-07-14 15:18 ` Paul Gortmaker
[not found] ` <20160714151835.GO4194@windriver.com>
2016-07-14 18:39 ` Ingo Molnar
[not found] ` <20160714183903.GA16975@gmail.com>
2016-07-14 18:46 ` Paul Gortmaker
[not found] ` <20160714184603.GR4194@windriver.com>
2016-07-14 18:56 ` Ingo Molnar [this message]
2016-07-14 0:18 Paul Gortmaker
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='20160714185621.GA21092__31409.0663604022$1468522668$gmane$org@gmail.com' \
--to=mingo@kernel.org \
--cc=arjan@linux.intel.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paul.gortmaker@windriver.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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 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).