From: Elie De Brauwer <eliedebrauwer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Elie De Brauwer
<eliedebrauwer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: [PATCH 0/3] mem.4 updates
Date: Fri, 2 Jan 2015 14:11:35 +0100 [thread overview]
Message-ID: <1420204298-25625-1-git-send-email-eliedebrauwer@gmail.com> (raw)
Hello Michael,
Attached are three patches which modify mem.4:
- One explains that /dev/kmem is only accessisble if CONFIG_DEVKMEM is set
- Another one which fixes an error in the group name used in the example
to create /dev/port.
- A last one which explains the impact of the CONFIG_STRICT_DEVMEM option
on /dev/mem.
my 2 cents
E.
Elie De Brauwer (3):
mem.4: /dev/kmem depends on CONFIG_DEVKMEM
mem.4: correct /dev/port group in example
mem.4: Add CONFIG_STRICT_DEVMEM
man4/mem.4 | 14 ++++++++++++--
1 file changed, 12 insertions(+), 2 deletions(-)
--
2.1.3
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2015-01-02 13:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-02 13:11 Elie De Brauwer [this message]
[not found] ` <1420204298-25625-1-git-send-email-eliedebrauwer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-01-02 13:11 ` [PATCH 1/3] mem.4: /dev/kmem depends on CONFIG_DEVKMEM Elie De Brauwer
[not found] ` <1420204298-25625-2-git-send-email-eliedebrauwer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-01-06 10:41 ` Michael Kerrisk (man-pages)
2015-01-02 13:11 ` [PATCH 2/3] mem.4: correct /dev/port group in example Elie De Brauwer
[not found] ` <1420204298-25625-3-git-send-email-eliedebrauwer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-01-06 10:44 ` Michael Kerrisk (man-pages)
2015-01-02 13:11 ` [PATCH 3/3] mem.4: Add CONFIG_STRICT_DEVMEM Elie De Brauwer
[not found] ` <1420204298-25625-4-git-send-email-eliedebrauwer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-01-06 10:50 ` Michael Kerrisk (man-pages)
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=1420204298-25625-1-git-send-email-eliedebrauwer@gmail.com \
--to=eliedebrauwer-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).