Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: hch@infradead.org (Christoph Hellwig)
To: linux-riscv@lists.infradead.org
Subject: [PATCH] riscv: enable STRICT_DEVMEM by default
Date: Thu, 22 Feb 2018 07:54:42 -0800	[thread overview]
Message-ID: <20180222155442.GA7838@infradead.org> (raw)
In-Reply-To: <1519314839.2861.1.camel@wdc.com>

On Thu, Feb 22, 2018 at 03:54:01PM +0000, Bart Van Assche wrote:
> On Thu, 2018-02-22 at 07:39 -0800, Christoph Hellwig wrote:
> > No need to enable /dev/mem access on a new port.
> > 
> > Signed-off-by: Christoph Hellwig <hch@lst.de>
> > ---
> >  lib/Kconfig.debug | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
> > index 6088408ef26c..0c6c2aafe93a 100644
> > --- a/lib/Kconfig.debug
> > +++ b/lib/Kconfig.debug
> > @@ -1968,7 +1968,7 @@ config STRICT_DEVMEM
> >  	bool "Filter access to /dev/mem"
> >  	depends on MMU && DEVMEM
> >  	depends on ARCH_HAS_DEVMEM_IS_ALLOWED
> > -	default y if TILE || PPC || X86 || ARM64
> > +	default y if TILE || PPC || X86 || ARM64 | RISCV
>                                                  ^
> Did you perhaps intend "||" instead of "|"? With that change applied:
> 
> Reviewed-by: Bart Van Assche <bart.vanassche@wdc.com

Oops, yes.

  reply	other threads:[~2018-02-22 15:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-22 15:39 [PATCH] riscv: enable STRICT_DEVMEM by default Christoph Hellwig
2018-02-22 15:54 ` Bart Van Assche
2018-02-22 15:54   ` Christoph Hellwig [this message]
2018-02-26 18:04     ` Palmer Dabbelt
2018-02-26 17:48 ` Palmer Dabbelt

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=20180222155442.GA7838@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-riscv@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox