Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030250AbbKDOJ7 (ORCPT ); Wed, 4 Nov 2015 09:09:59 -0500 Received: from out5-smtp.messagingengine.com ([66.111.4.29]:45901 "EHLO out5-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932178AbbKDOJ5 (ORCPT ); Wed, 4 Nov 2015 09:09:57 -0500 X-Sasl-enc: kpsnmEQQGFFJ+IkoXv1dsmN3a0eYensO6e0FjCXFBXmS 1446646196 Subject: Re: [PATCH 3.12 16/33] isdn/gigaset: reset tty->receive_room when attaching ser_gigaset To: Paul Bolle 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> <56002B48.7090008@imap.cc> <1444165247.2417.74.camel@tiscali.nl> <561B7B01.40309@imap.cc> <1445245786.2581.28.camel@tiscali.nl> Cc: Peter Hurley , Jiri Slaby , linux-kernel@vger.kernel.org, "David S. Miller" From: Tilman Schmidt X-Enigmail-Draft-Status: N1110 Message-ID: <563A11A9.40601@imap.cc> Date: Wed, 4 Nov 2015 15:09:45 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <1445245786.2581.28.camel@tiscali.nl> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="O0Ths1cn6xXaobfmfXIffdsLD5XboIGap" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2467 Lines: 62 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --O0Ths1cn6xXaobfmfXIffdsLD5XboIGap Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Paul, Am 19.10.2015 um 11:09 schrieb Paul Bolle: > On ma, 2015-10-12 at 11:18 +0200, Tilman Schmidt wrote: >> While it doesn't make any sense indeed to run two instances of >> ldattach >> in parallel on one and the same serial port, it is entirely conceivabl= e >> that someone might do so inadvertently, by not being aware that one is= >> running already. >=20 > I'm wandering off topic a bit, but doesn't that imply that ldattach > should bail out with an error if someone tries to do that? I'm of two minds about this. On the pro side, it might prevent some surprises. But on the other hand, nothing actually breaks if someone does, and I'm not 100% sure there are really no legitimate scenarios. Add to this that I don't have a clear idea how to actually implement such a bailout, and that I'm really short of time. So I'm reluctant to tackle this topic. Perhaps the best way forward would be someone (not me) submitting a patch to ldattach, thereby triggering a discussion of the pros and cons that would ideally include all (or most) ldattach users and consider all line disciplines it is used with. --=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) --O0Ths1cn6xXaobfmfXIffdsLD5XboIGap 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 iQEcBAEBCAAGBQJWOhGyAAoJEFPuqx0v+F+qiEUIALoecYOoI9qpnZisyqILC1yt 4mNQz3b8+c4TFnBnJnlnNQ782u033WXM4qGd2E5gXclKIK0OzX+EclQ8tuI/bUpD pq1ndJjr7ep8+SPFfPHC5/ICCKd63koTMFqB1fv3lU9OeurLe4gaZfpTS2XONSfm 2wqFdFTPBOT+v/LjGA9GyzEQnAv/tgZJdPjd3yauSlumugyFi7OY5FFIniWAycUv 2SXSwC+0KXTD8Co/3uO+FzhUlT+LGsX8hfM9DuLrMFncGkweyT10JZCHMIPFtW58 b7rQBdwRWxwMdohn9dKGFAn2rJvbp5VuFaKixYHPWYdXhHpT9/G6lON5aWWxmGs= =rNNL -----END PGP SIGNATURE----- --O0Ths1cn6xXaobfmfXIffdsLD5XboIGap-- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/