From: Catalin Marinas <catalin.marinas@arm.com>
To: Laura Abbott <lauraa@codeaurora.org>
Cc: Will Deacon <Will.Deacon@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: Add missing Kconfig for CONFIG_STRICT_DEVMEM
Date: Mon, 7 Apr 2014 17:35:45 +0100 [thread overview]
Message-ID: <20140407163545.GB8479@arm.com> (raw)
In-Reply-To: <1396657850-14252-1-git-send-email-lauraa@codeaurora.org>
On Sat, Apr 05, 2014 at 01:30:50AM +0100, Laura Abbott wrote:
> The Kconfig for CONFIG_STRICT_DEVMEM is missing despite being
> used in mmap.c. Add it.
>
> Signed-off-by: Laura Abbott <lauraa@codeaurora.org>
Thanks. Applied.
--
Catalin
prev parent reply other threads:[~2014-04-07 16:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-05 0:30 [PATCH] arm64: Add missing Kconfig for CONFIG_STRICT_DEVMEM Laura Abbott
2014-04-07 16:35 ` Catalin Marinas [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=20140407163545.GB8479@arm.com \
--to=catalin.marinas@arm.com \
--cc=Will.Deacon@arm.com \
--cc=lauraa@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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).