From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com ([66.111.4.25]:53514 "EHLO out1-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756913AbbIURbw (ORCPT ); Mon, 21 Sep 2015 13:31:52 -0400 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 4E05220D44 for ; Mon, 21 Sep 2015 13:31:51 -0400 (EDT) Subject: Re: [PATCH 3.12 16/33] isdn/gigaset: reset tty->receive_room when attaching ser_gigaset To: Peter Hurley References: <350624fa32cb152bfec51f236b0b62b8d480a05a.1442326825.git.jslaby@suse.cz> <4a187391f4c7d54b9c07eed08de48ffd6e0a3f20.1442326825.git.jslaby@suse.cz> <55F8B9D9.5060201@imap.cc> <55F951EA.1060001@imap.cc> <55FC05C7.1000207@imap.cc> <5600028B.4050904@hurleysoftware.com> <56000871.40700@imap.cc> <56003642.3050404@hurleysoftware.com> Cc: Jiri Slaby , "stable@vger.kernel.org" , Linux kernel mailing list , "David S. Miller" From: Tilman Schmidt Message-ID: <56003EF1.8070405@imap.cc> Date: Mon, 21 Sep 2015 19:31:29 +0200 MIME-Version: 1.0 In-Reply-To: <56003642.3050404@hurleysoftware.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="pQPkKP0knKFdEuqWxNTaq5uWHENreDLpe" Sender: stable-owner@vger.kernel.org List-ID: This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --pQPkKP0knKFdEuqWxNTaq5uWHENreDLpe Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Am 21.09.2015 um 18:54 schrieb Peter Hurley: > 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 wr= ote: >> [...] >>>>>> - The requirement for line disciplines to set receive_room wasn't = (and >>>>>> btw still isn't) documented anywhere, so it's unlikely anything ac= tively >>>>>> 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. >=20 > I vaguely recall that. A quick search reminded me there were unaddresse= d > comments wrt that patch: https://lkml.org/lkml/2015/7/14/608 Ah, so that's the blocking condition? How can I address that comment in order to unblock that patch? --=20 Tilman Schmidt E-Mail: tilman@imap.cc Bonn, Germany Diese Nachricht besteht zu 100% aus wiederverwerteten Bits. Unge=C3=B6ffnet mindestens haltbar bis: (siehe R=C3=BCckseite) --pQPkKP0knKFdEuqWxNTaq5uWHENreDLpe Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWAD8FAAoJEFPuqx0v+F+qBX8IAJe74DrS+Sc6mjONGkzhgVMM lsG5Veq8zl0SJ82lGuo5gv9zC4uYBovsCrnAU+aRKpV1eEx0HkTtjUFQWC72TPlW 6k8sWJB0wPv9nmXJGiOU3RoBnd58wmKrTWqKROCBzTdO7Pm/1Po11cKOnyNzaGSI mY5A6TYIXkAe40kfNZb5mz3nGlrrKKEWbX19Q0Lj/rCc8JyPFAc+YsDbrdM00s3J CzA8kmtD05h7WCr3rg2GAnbzRDEUXc6LO+YRKNBQUDc7JP8zea6DMkADN+bNCA1G oOcjnh2YW2sfK2aCtM1HiJZ/NVqYnBu11yW6Nwk0kNO3Oqqa7773dC2Xm34jaMk= =S9KN -----END PGP SIGNATURE----- --pQPkKP0knKFdEuqWxNTaq5uWHENreDLpe--