From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stable-owner@vger.kernel.org>
Received: from mail-qg0-f41.google.com ([209.85.192.41]:36838 "EHLO
	mail-qg0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S932576AbbIUQya (ORCPT
	<rfc822;stable@vger.kernel.org>); Mon, 21 Sep 2015 12:54:30 -0400
Received: by qgx61 with SMTP id 61so94458503qgx.3
        for <stable@vger.kernel.org>; Mon, 21 Sep 2015 09:54:29 -0700 (PDT)
Subject: Re: [PATCH 3.12 16/33] isdn/gigaset: reset tty->receive_room when
 attaching ser_gigaset
To: Tilman Schmidt <tilman@imap.cc>
References: <cover.1442326825.git.jslaby@suse.cz>
 <350624fa32cb152bfec51f236b0b62b8d480a05a.1442326825.git.jslaby@suse.cz>
 <4a187391f4c7d54b9c07eed08de48ffd6e0a3f20.1442326825.git.jslaby@suse.cz>
 <CAKU3ayUyyYZzDr-AiZEW7uy=kwTtNptnOZMAKEYyn+=dd_47bg@mail.gmail.com>
 <55F8B9D9.5060201@imap.cc>
 <CAKU3ayVBUODUtiZS77gdzMg0R7kD8pgGu60Sdk=CRDBGt4iBQw@mail.gmail.com>
 <55F951EA.1060001@imap.cc>
 <CAKU3ayWYGBJ_E4vCnGoCc+vRUO9a0WNujZYbxwE+4QUJehmGsA@mail.gmail.com>
 <55FC05C7.1000207@imap.cc> <5600028B.4050904@hurleysoftware.com>
 <56000871.40700@imap.cc>
Cc: Jiri Slaby <jslaby@suse.cz>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	Linux kernel mailing list <linux-kernel@vger.kernel.org>,
	"David S. Miller" <davem@davemloft.net>
From: Peter Hurley <peter@hurleysoftware.com>
Message-ID: <56003642.3050404@hurleysoftware.com>
Date: Mon, 21 Sep 2015 12:54:26 -0400
MIME-Version: 1.0
In-Reply-To: <56000871.40700@imap.cc>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Sender: stable-owner@vger.kernel.org
List-ID: <stable.vger.kernel.org>

On 09/21/2015 09:38 AM, Tilman Schmidt wrote:
> Am 21.09.2015 um 15:13 schrieb Peter Hurley:
>> On 09/18/2015 08:38 AM, Tilman Schmidt wrote:
>>> Am 17.09.2015 um 20:13 schrieb Peter Hurley:
>>>> On Wed, Sep 16, 2015 at 7:26 AM, Tilman Schmidt <tilman@imap.cc> wrote:
> [...]
>>>>> - The requirement for line disciplines to set receive_room wasn't (and
>>>>> btw still isn't) documented anywhere, so it's unlikely anything actively
>>>>> relied on it.
>>>>
>>>> Nevertheless, that is the requirement, and what every other in-tree line
>>>> discipline does.
>>>
>>> Your word for it. Still I don't understand the curious resistance to
>>> documenting it. If it is the requirement, why keep it secret?
>>
>> Nothing sinister here :)
>>
>> Feel free to submit documentation patches.
> 
> I already did. For some unknown reason nobody wants to merge them.

I vaguely recall that. A quick search reminded me there were unaddressed
comments wrt that patch:  https://lkml.org/lkml/2015/7/14/608

Regards,
Peter Hurley