From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
mpe@ellerman.id.au, mingo@kernel.org
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 1/2] Documentation/features: Add na key to arch-support.txt
Date: Sun, 19 Jul 2015 14:21:55 +0900 [thread overview]
Message-ID: <55AB33F3.30307@hitachi.com> (raw)
In-Reply-To: <20150717105139.29162.31467.stgit@thinktux.in.ibm.com>
On 2015/07/17 19:51, Ananth N Mavinakayanahalli wrote:
> To be used for features we will not support on a particular architecture.
> The git log that adds this needs to provide the justification 'why?'
>
> Signed-off-by: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
> ---
> Documentation/features/arch-support.txt | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/features/arch-support.txt b/Documentation/features/arch-support.txt
> index d22a109..f2b272e 100644
> --- a/Documentation/features/arch-support.txt
> +++ b/Documentation/features/arch-support.txt
> @@ -8,4 +8,5 @@ The meaning of entries in the tables is:
> | ok | # feature supported by the architecture
> |TODO| # feature not yet supported by the architecture
> | .. | # feature cannot be supported by the hardware
> + | na | # feature will not be supported by the architecture
"will not" sounds like someone's will. I guess it could be "feature is useless/needless
on the architecture".
Thank you,
--
Masami HIRAMATSU
Linux Technology Research Center, System Productivity Research Dept.
Center for Technology Innovation - Systems Engineering
Hitachi, Ltd., Research & Development Group
E-mail: masami.hiramatsu.pt@hitachi.com
prev parent reply other threads:[~2015-07-19 5:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 10:51 [PATCH V2 1/2] Documentation/features: Add na key to arch-support.txt Ananth N Mavinakayanahalli
2015-07-17 10:52 ` [PATCH V2 2/2] kprobes: Mark OPTPROBES na for powerpc Ananth N Mavinakayanahalli
2015-07-19 5:21 ` Masami Hiramatsu [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=55AB33F3.30307@hitachi.com \
--to=masami.hiramatsu.pt@hitachi.com \
--cc=ananth@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@kernel.org \
--cc=mpe@ellerman.id.au \
/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).