From: "Chang S. Bae" <chang.seok.bae@intel.com>
To: "Luck, Tony" <tony.luck@intel.com>,
"Hansen, Dave" <dave.hansen@intel.com>,
"Brown, Len" <len.brown@intel.com>,
"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
"Chatre, Reinette" <reinette.chatre@intel.com>,
"Williams, Dan J" <dan.j.williams@intel.com>
Cc: "bagasdotme@gmail.com" <bagasdotme@gmail.com>,
"corbet@lwn.net" <corbet@lwn.net>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-man@vger.kernel.org" <linux-man@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/2] x86: AMX enabling example with new constants
Date: Thu, 21 Jul 2022 13:57:42 -0700 [thread overview]
Message-ID: <cd56a293-6353-c57a-56c7-adb5b3052848@intel.com> (raw)
In-Reply-To: <SJ1PR11MB6083E042762320A642D1FC5AFC919@SJ1PR11MB6083.namprd11.prod.outlook.com>
On 7/21/2022 1:53 PM, Luck, Tony wrote:
>> The arch_prctl(2) manual page [2] is missing these new options. Perhaps,
>> the man-page update follows up along with this.
>
> This isn't the right process to get a manual page updated.
>
> See:
>
> https://www.kernel.org/doc/man-pages/contributing.html
>
> then log a bug, write a patch, and submit it to add the AMX options.
Indeed. I didn't intend this series to initiate the process to update
the man page. Instead, I wanted to establish the kernel doc before
starting it. But it looks like not super clear, sorry.
Thanks,
Chang
prev parent reply other threads:[~2022-07-21 20:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 17:13 Chang S. Bae
2022-07-11 17:13 ` [PATCH v3 1/2] x86/arch_prctl: Add AMX feature numbers as ABI constants Chang S. Bae
2022-07-11 17:13 ` [PATCH v3 2/2] Documentation/x86: Add the AMX enabling example Chang S. Bae
2022-07-21 20:53 ` [PATCH v3 0/2] x86: AMX enabling example with new constants Luck, Tony
2022-07-21 20:57 ` Chang S. Bae [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=cd56a293-6353-c57a-56c7-adb5b3052848@intel.com \
--to=chang.seok.bae@intel.com \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@intel.com \
--cc=len.brown@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=reinette.chatre@intel.com \
--cc=tony.luck@intel.com \
/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
all inboxes | Powered by JetHome®