public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: linux-kernel@vger.kernel.org, kernel@pengutronix.de,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jslaby@suse.com>
Subject: Re: tty: closing n_gsm line discipline always times out
Date: Fri, 19 May 2017 13:58:40 +0100	[thread overview]
Message-ID: <20170519135840.46da3df0@alans-desktop> (raw)
In-Reply-To: <20170518065059.keq42z4g64ymaeaw@pengutronix.de>

> This option doesn't sound very nice because then userspace needs to know
> details of the protocol that it just wants to use. Also the cleanup
> won't be done if the userspace process is killed for some reason.

The same is basically true of an ioctl unfortunately.

Alan

      reply	other threads:[~2017-05-19 12:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-17 13:44 tty: closing n_gsm line discipline always times out Sascha Hauer
2017-05-17 15:23 ` Alan Cox
2017-05-18  6:50   ` Sascha Hauer
2017-05-19 12:58     ` Alan Cox [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=20170519135840.46da3df0@alans-desktop \
    --to=gnomes@lxorguk.ukuu.org.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=s.hauer@pengutronix.de \
    /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