From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] arm64:add missing CONFIG_STRICT_KERNEL_RWX for mark_rodata_ro
Date: Tue, 29 May 2018 16:45:24 +0100 [thread overview]
Message-ID: <20180529154523.GK17159@arm.com> (raw)
In-Reply-To: <20180529133615.26889-1-nixiaoming@huawei.com>
On Tue, May 29, 2018 at 09:36:15PM +0800, nixiaoming wrote:
> mark_rodata_ro is only called by the function mark_readonly when
> CONFIG_STRICT_KERNEL_RWX=y,
> if CONFIG_STRICT_KERNEL_RWX is not set
> a compile warning may be triggered: unused function
How are you achieving this configuration? In our Kconfig we select this
unconditionally.
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: nixiaoming <nixiaoming@huawei.com>
Cc: catalin.marinas@arm.com, ard.biesheuvel@linaro.org,
marc.zyngier@arm.com, james.morse@arm.com,
kristina.martsenko@arm.com, steve.capper@arm.com,
tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
akpm@linux-foundation.org, vbabka@suse.cz, mhocko@suse.com,
dave.hansen@linux.intel.com, dan.j.williams@intel.com,
kirill.shutemov@linux.intel.com, zhang.jia@linux.alibaba.com,
schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, x86@kernel.org,
linux-s390@vger.kernel.org
Subject: Re: [PATCH 1/3] arm64:add missing CONFIG_STRICT_KERNEL_RWX for mark_rodata_ro
Date: Tue, 29 May 2018 16:45:24 +0100 [thread overview]
Message-ID: <20180529154523.GK17159@arm.com> (raw)
In-Reply-To: <20180529133615.26889-1-nixiaoming@huawei.com>
On Tue, May 29, 2018 at 09:36:15PM +0800, nixiaoming wrote:
> mark_rodata_ro is only called by the function mark_readonly when
> CONFIG_STRICT_KERNEL_RWX=y,
> if CONFIG_STRICT_KERNEL_RWX is not set
> a compile warning may be triggered: unused function
How are you achieving this configuration? In our Kconfig we select this
unconditionally.
Will
next prev parent reply other threads:[~2018-05-29 15:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 13:36 [PATCH 1/3] arm64:add missing CONFIG_STRICT_KERNEL_RWX for mark_rodata_ro nixiaoming
2018-05-29 13:36 ` nixiaoming
2018-05-29 15:45 ` Will Deacon [this message]
2018-05-29 15:45 ` Will Deacon
2018-05-30 3:31 ` Nixiaoming
2018-05-30 3:31 ` Nixiaoming
2018-05-30 8:08 ` Mark Rutland
2018-05-30 8:08 ` Mark Rutland
2018-05-30 9:05 ` Nixiaoming
2018-05-30 9:05 ` Nixiaoming
-- strict thread matches above, loose matches on Subject: below --
2018-05-28 3:33 nixiaoming
2018-05-28 3:33 ` nixiaoming
2018-05-29 9:21 ` Will Deacon
2018-05-29 9:21 ` Will Deacon
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=20180529154523.GK17159@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.