From: Jonathan Corbet <corbet@lwn.net>
To: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: rs485: Do not define manually the ioctl
Date: Thu, 18 Aug 2016 11:08:51 -0600 [thread overview]
Message-ID: <20160818110851.04bc0ab5@lwn.net> (raw)
In-Reply-To: <1471510459-8142-1-git-send-email-ricardo.ribalda@gmail.com>
On Thu, 18 Aug 2016 10:54:19 +0200
Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com> wrote:
> It is not a very good practice to define the IOCTL manually instead of
> using the header file.
>
> Fix it on the documentation example.
Makes sense to me; applied to the docs tree, thanks.
jon
prev parent reply other threads:[~2016-08-19 1:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 8:54 [PATCH] Documentation: rs485: Do not define manually the ioctl Ricardo Ribalda Delgado
2016-08-18 17:08 ` Jonathan Corbet [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=20160818110851.04bc0ab5@lwn.net \
--to=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ricardo.ribalda@gmail.com \
/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