From: Borislav Petkov <bp@alien8.de>
To: Kyung Min Park <kyung.min.park@intel.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org, tglx@linutronix.de,
tony.luck@intel.com, dave.hansen@intel.com,
ricardo.neri@intel.com, hpa@zytor.com,
gregkh@linuxfoundation.org, ak@linux.intel.com,
ravi.v.shankar@intel.com,
Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
Subject: Re: [PATCH v2] Documentation/x86: Add documentation for /proc/cpuinfo feature flags
Date: Sun, 30 Aug 2020 13:50:24 +0200 [thread overview]
Message-ID: <20200830115024.GA4297@zn.tnic> (raw)
In-Reply-To: <b171209faab7e141a9988ecf47fa55bf855cb664.camel@intel.com>
On Fri, Aug 28, 2020 at 03:30:32PM -0700, Kyung Min Park wrote:
> Should I mention the tool specifically although the tool is WIP?
Well, if you wanna look at it that way, the whole kernel is constantly
and forever WIP. :-)
Also, if there's some functionality missing, pointing to it might make
people send patches.
> As you commented previously, should I use
> tools/arch/x86/tools/cpuid/cpuid as the future tool and its location?
Yeah, let's just drop the second "tools", i.e.,
tools/arch/x86/kcpuid/
or so should be good enough.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2020-08-30 11:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 18:04 [PATCH v2] Documentation/x86: Add documentation for /proc/cpuinfo feature flags Kyung Min Park
2020-08-28 18:42 ` Borislav Petkov
2020-08-28 22:30 ` Kyung Min Park
2020-08-30 11:50 ` Borislav Petkov [this message]
2020-08-30 21:21 ` Kyung Min Park
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=20200830115024.GA4297@zn.tnic \
--to=bp@alien8.de \
--cc=ak@linux.intel.com \
--cc=dave.hansen@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=kyung.min.park@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ravi.v.shankar@intel.com \
--cc=ricardo.neri-calderon@linux.intel.com \
--cc=ricardo.neri@intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--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