From: "Reimar Döffinger" <Reimar.Doeffinger@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cdrom.c: Only read a cdrom_msf0 struct from userspace.
Date: Sat, 19 Apr 2014 10:13:56 +0000 (UTC) [thread overview]
Message-ID: <loom.20140419T120955-590@post.gmane.org> (raw)
In-Reply-To: <loom.20140327T204517-831@post.gmane.org>
Reimar Döffinger <Reimar.Doeffinger <at> gmx.de> writes:
> ping
> Having one piece of documentation that is clearly utter nonsense and then a
> second piece of documentation that adds a note that the first documentation
> is wrong sure isn't the way to keep things.
ping2
prev parent reply other threads:[~2014-04-19 10:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-15 13:53 Reimar Döffinger
2014-03-27 19:48 ` Reimar Döffinger
2014-04-19 10:13 ` Reimar Döffinger [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=loom.20140419T120955-590@post.gmane.org \
--to=reimar.doeffinger@gmx.de \
--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
all inboxes | Powered by JetHome®