From: Timur Tabi <timur@freescale.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Typo in tty_driver.h?
Date: Thu, 28 Oct 2010 16:22:34 -0500 [thread overview]
Message-ID: <4CC9E99A.3070903@freescale.com> (raw)
I believe I found a typo in a comment in tty_driver.h
* TTY_DRIVER_DYNAMIC_DEV --- if set, the individual tty devices need
* to be registered with a call to tty_register_driver() when the
* device is found in the system and unregistered with a call to
* tty_unregister_device() so the devices will be show up
* properly in sysfs. If not set, driver->num entries will be
* created by the tty core in sysfs when tty_register_driver() is
* called. This is to be used by drivers that have tty devices
* that can appear and disappear while the main tty driver is
* registered with the tty core.
On line 2, I think it should say "tty_register_device()" instead of
"tty_register_driver()".
--
Timur Tabi
Linux kernel developer at Freescale
next reply other threads:[~2010-10-28 21:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 21:22 Timur Tabi [this message]
2010-10-31 7:42 ` Typo in tty_driver.h? Jiri Slaby
2010-10-31 13:24 ` Tabi Timur-B04825
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=4CC9E99A.3070903@freescale.com \
--to=timur@freescale.com \
--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