Re: [patch 0/3] Re: tty contention resulting from tty_open_by_device export

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Okash Khawaja <okash.khawaja@xxxxxxxxx>
Subject: Re: [patch 0/3] Re: tty contention resulting from tty_open_by_device export
From: Alan Cox <gnomes@xxxxxxxxxxxxxxxxxxx>
Date: Tue, 18 Jul 2017 14:49:31 +0100
Cc: "devel@xxxxxxxxxxxxxxxxxxxx" <devel@xxxxxxxxxxxxxxxxxxxx>, Kirk Reiser <kirk@xxxxxxxxxx>, Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>, "speakup@xxxxxxxxxxxxxxxxx" <speakup@xxxxxxxxxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, Jiri Slaby <jslaby@xxxxxxxx>, Samuel Thibault <samuel.thibault@xxxxxxxxxxxx>, Chris Brannon <chris@xxxxxxxxxxxxxxxx>
In-reply-to: <20170718112952.GA564@sanghar>
Organization: Intel Corporation
References: <20170708083803.GA23080@kroah.com> <20170709114153.157783481@gmail.com> <20170710125233.2006733e@alans-desktop> <20170710123307.GA777@sanghar> <20170712192028.70bc0d54@alans-desktop> <20170713112954.GA665@sanghar> <20170717123145.GE24503@kroah.com> <3E107A3D-D8E2-43E5-8DCB-F9DE2F5AAAEA@gmail.com> <20170717230438.5c3bd397@alans-desktop> <20170718112952.GA564@sanghar>

> The patch is untested but I can work on this if that fits in with the
> plans for tty.

I think this is the right direction.

Alan

_______________________________________________
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxx
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

Follow-Ups:
- [patch v3 0/3] tty contention resulting from tty_open_by_driver export
  - From: Okash Khawaja

References:
- Re: tty contention resulting from tty_open_by_device export
  - From: Greg Kroah-Hartman
- [patch 0/3] Re: tty contention resulting from tty_open_by_device export
  - From: Okash Khawaja
- Re: [patch 0/3] Re: tty contention resulting from tty_open_by_device export
  - From: Alan Cox
- Re: [patch 0/3] Re: tty contention resulting from tty_open_by_device export
  - From: Okash Khawaja
- Re: [patch 0/3] Re: tty contention resulting from tty_open_by_device export
  - From: Alan Cox
- Re: [patch 0/3] Re: tty contention resulting from tty_open_by_device export
  - From: Okash Khawaja
- Re: [patch 0/3] Re: tty contention resulting from tty_open_by_device export
  - From: Greg Kroah-Hartman
- Re: [patch 0/3] Re: tty contention resulting from tty_open_by_device export
  - From: Okash Khawaja
- Re: [patch 0/3] Re: tty contention resulting from tty_open_by_device export
  - From: Alan Cox
- Re: [patch 0/3] Re: tty contention resulting from tty_open_by_device export
  - From: Okash Khawaja

Prev by Date: [PATCH v2 8/8] staging: fsl-mc: allow the driver compile multi-arch
Next by Date: Re: [PATCH 4/4] staging: wlan-ng: prism2sta: Use 'in situ' endian conversions in 'prism2sta_inf_chinforesults()'
Previous by thread: Re: [patch 0/3] Re: tty contention resulting from tty_open_by_device export
Next by thread: [patch v3 0/3] tty contention resulting from tty_open_by_driver export
Index(es):
- Date
- Thread

[Index of Archives] [Linux Driver Backports] [DMA Engine] [Linux GPIO] [Linux SPI] [Video for Linux] [Linux USB Devel] [Linux Coverity] [Linux Audio Users] [Linux Kernel] [Linux SCSI] [Yosemite Backpacking]