From: Michael Ellerman <mpe@ellerman.id.au>
To: Bhupesh Sharma <bhsharma@redhat.com>, linuxppc-dev@lists.ozlabs.org
Cc: arnd@arndb.de, corbet@lwn.net, bhsharma@redhat.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
paulus@samba.org, bhupesh.linux@gmail.com
Subject: Re: [PATCH] Documentation/stackprotector: powerpc supports stack protector
Date: Thu, 30 May 2019 22:55:10 +1000 [thread overview]
Message-ID: <87v9xsnlu9.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <1559212177-7072-1-git-send-email-bhsharma@redhat.com>
Bhupesh Sharma <bhsharma@redhat.com> writes:
> powerpc architecture (both 64-bit and 32-bit) supports stack protector
> mechanism since some time now [see commit 06ec27aea9fc ("powerpc/64:
> add stack protector support")].
>
> Update stackprotector arch support documentation to reflect the same.
>
> Signed-off-by: Bhupesh Sharma <bhsharma@redhat.com>
> ---
> Documentation/features/debug/stackprotector/arch-support.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/features/debug/stackprotector/arch-support.txt b/Documentation/features/debug/stackprotector/arch-support.txt
> index 9999ea521f3e..32bbdfc64c32 100644
> --- a/Documentation/features/debug/stackprotector/arch-support.txt
> +++ b/Documentation/features/debug/stackprotector/arch-support.txt
> @@ -22,7 +22,7 @@
> | nios2: | TODO |
> | openrisc: | TODO |
> | parisc: | TODO |
> - | powerpc: | TODO |
> + | powerpc: | ok |
> | riscv: | TODO |
> | s390: | TODO |
> | sh: | ok |
> --
> 2.7.4
Thanks.
This should probably go via the documentation tree?
Acked-by: Michael Ellerman <mpe@ellerman.id.au>
cheers
next prev parent reply other threads:[~2019-05-30 12:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 10:29 [PATCH] Documentation/stackprotector: powerpc supports stack protector Bhupesh Sharma
2019-05-30 12:55 ` Michael Ellerman [this message]
2019-05-30 13:07 ` Bhupesh Sharma
2019-05-30 14:13 ` Jonathan Corbet
2019-05-31 15:13 ` Michael Ellerman
2019-06-05 9:41 ` Bhupesh Sharma
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=87v9xsnlu9.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=arnd@arndb.de \
--cc=bhsharma@redhat.com \
--cc=bhupesh.linux@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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).