From: David Howells <dhowells@redhat.com>
To: Bernhard Walle <bwalle@suse.de>
Cc: dhowells@redhat.com, Alan Cox <alan@lxorguk.ukuu.org.uk>,
x86@kernel.org, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org, crash-utility@redhat.com
Subject: Re: [PATCH 3/3] Remove CONFIG_STRICT_DEVMEM
Date: Mon, 17 Nov 2008 13:57:38 +0000 [thread overview]
Message-ID: <32168.1226930258@redhat.com> (raw)
In-Reply-To: <20081116162149.07f05c7c@kopernikus.site>
Bernhard Walle <bwalle@suse.de> wrote:
> For embedded users, do they use CONFIG_SYSCTL at all?
Yes. It still allows you to configure various things about the kernel.
David
next prev parent reply other threads:[~2008-11-17 13:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-16 14:47 Turn CONFIG_STRICT_DEVMEM in sysctl dev.mem.restricted Bernhard Walle
2008-11-16 14:47 ` [PATCH 1/3] Unify devmem_is_allowed across architectures Bernhard Walle
2008-11-16 14:47 ` [PATCH 2/3] Add dev.mem.restricted sysctl Bernhard Walle
2008-11-16 14:47 ` Bernhard Walle
2008-11-16 15:07 ` Willy Tarreau
2008-11-16 14:47 ` [PATCH 3/3] Remove CONFIG_STRICT_DEVMEM Bernhard Walle
2008-11-16 15:09 ` Alan Cox
2008-11-16 15:09 ` Alan Cox
2008-11-16 15:09 ` Alan Cox
2008-11-16 15:21 ` Bernhard Walle
2008-11-16 15:46 ` Alan Cox
2008-11-16 15:46 ` Alan Cox
2008-11-17 13:57 ` David Howells [this message]
2008-11-16 15:07 ` Turn CONFIG_STRICT_DEVMEM in sysctl dev.mem.restricted Alan Cox
2008-11-16 15:07 ` Alan Cox
2008-11-16 15:07 ` Alan Cox
2008-11-16 15:20 ` Bernhard Walle
2008-11-16 15:45 ` Alan Cox
2008-11-16 15:45 ` Alan Cox
2008-11-16 16:03 ` Arjan van de Ven
2008-11-16 16:09 ` Alan Cox
2008-11-16 16:09 ` Alan Cox
2008-11-16 16:19 ` Bernhard Walle
2008-11-16 16:11 ` Bernhard Walle
2008-11-16 17:03 ` Alan Cox
2008-11-16 17:03 ` Alan Cox
2008-11-16 15:39 ` Arjan van de Ven
2008-11-16 15:39 ` Arjan van de Ven
2008-11-16 15:39 ` Arjan van de Ven
2008-11-16 15:56 ` Bernhard Walle
2008-11-16 16:06 ` Arjan van de Ven
2008-11-16 20:32 ` H. Peter Anvin
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=32168.1226930258@redhat.com \
--to=dhowells@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bwalle@suse.de \
--cc=crash-utility@redhat.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@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 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.