Linux Documentation
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@suse.de>
To: Dave Hansen <dave.hansen@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, patches@lists.linux.dev,
	corbet@lwn.net, tglx@linutronix.de, x86@kernel.org,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH] [v2] x86/configs: Add x86 debugging Kconfig fragment plus docs
Date: Fri, 1 Apr 2022 19:57:51 +0200	[thread overview]
Message-ID: <Ykc9H801hkMRUd8t@zn.tnic> (raw)
In-Reply-To: <20220331175728.299103A0@davehans-spike.ostc.intel.com>

On Thu, Mar 31, 2022 at 10:57:28AM -0700, Dave Hansen wrote:
> 
> Changes from v1:
> 
>  * Add actual .config fragment instead of just documenting it
>  * Note that these partially x86-specific, but the rest can be
>    used to test all tip contributions.

Good, that looks nice. I'll queue it next week with this hunk added:

---
diff --git a/arch/x86/Makefile b/arch/x86/Makefile
index 63d50f65b828..1abd7cc9d6cd 100644
--- a/arch/x86/Makefile
+++ b/arch/x86/Makefile
@@ -313,5 +313,6 @@ define archhelp
   echo  ''
   echo  '  kvm_guest.config	- Enable Kconfig items for running this kernel as a KVM guest'
   echo  '  xen.config		- Enable Kconfig items for running this kernel as a Xen guest'
+  echo  '  x86_debug.config	- Enable tip tree debugging options for testing'
 
 endef

-- 
Regards/Gruss,
    Boris.

SUSE Software Solutions Germany GmbH, GF: Ivo Totev, HRB 36809, AG Nürnberg

      reply	other threads:[~2022-04-01 17:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-31 17:57 [PATCH] [v2] x86/configs: Add x86 debugging Kconfig fragment plus docs Dave Hansen
2022-04-01 17:57 ` Borislav Petkov [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=Ykc9H801hkMRUd8t@zn.tnic \
    --to=bp@suse.de \
    --cc=corbet@lwn.net \
    --cc=dave.hansen@linux.intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@lists.linux.dev \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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