From: Jiri Slaby <jslaby@suse.cz>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: shijie8@gmail.com, linux-serial@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tty: move the async flags from the serial code into the tty includes
Date: Wed, 22 Aug 2012 14:19:49 +0200 [thread overview]
Message-ID: <5034CE65.7040607@suse.cz> (raw)
In-Reply-To: <20120821133455.9090.24759.stgit@localhost.localdomain>
On 08/21/2012 03:35 PM, Alan Cox wrote:
> From: Alan Cox <alan@linux.intel.com>
>
> These are used with the tty_port flags which are tty generic so move the
> flags into a more sensible place. This then makes it possible to add
> helpers such as those suggested by Huang Shijie.
Yes, the idea looks good to me. I was actually thinking of the same.
But there are two issues with this patch (see below).
> --- a/include/linux/serial.h
> +++ b/include/linux/serial.h
> @@ -15,6 +15,8 @@
> #ifdef __KERNEL__
> #include <asm/page.h>
>
> +#include <linux/tty_flags.h>
> +
There are no minus lines in serial.h -- we have two copies of the flags
now? That looks insane.
The flags are a user API. You concealed them by the #include inside the
__KERNEL__ section (if I consider we do not have the flags defined twice).
And if we move the include outside of the __KERNEL__ section, we shall
update Kconfig, so that the new header is installed.
> /*
> * Counters of the input lines (CTS, DSR, RI, CD) interrupts
> */
> diff --git a/include/linux/tty.h b/include/linux/tty.h
> index 69a787f..dbebd1e 100644
> --- a/include/linux/tty.h
> +++ b/include/linux/tty.h
> @@ -43,6 +43,7 @@
> #include <linux/tty_driver.h>
> #include <linux/tty_ldisc.h>
> #include <linux/mutex.h>
> +#include <linux/tty_flags.h>
thanks,
--
js
suse labs
next prev parent reply other threads:[~2012-08-22 12:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 13:35 [PATCH] tty: move the async flags from the serial code into the tty includes Alan Cox
2012-08-21 15:13 ` Huang Shijie
2012-08-22 2:40 ` Huang Shijie
2012-08-22 12:19 ` Jiri Slaby [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-08-22 11:15 Alan Cox
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=5034CE65.7040607@suse.cz \
--to=jslaby@suse.cz \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=shijie8@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