From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756483AbcBWA2f (ORCPT ); Mon, 22 Feb 2016 19:28:35 -0500 Received: from mail.tnode.com ([46.54.226.45]:46680 "EHLO mail.tnode.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756081AbcBWA2e (ORCPT ); Mon, 22 Feb 2016 19:28:34 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 23 Feb 2016 00:28:32 +0000 From: Andrej Krpic To: One Thousand Gnomes Cc: , , Subject: Re: [PATCH 0/8] tty: =?UTF-8?Q?n=5Fgsm=3A=20Make=20mux=20work=20a?= =?UTF-8?Q?s=20a=20responder=20station?= In-Reply-To: <20160221234244.175a445c@lxorguk.ukuu.org.uk> References: <1456090717-19913-1-git-send-email-ak77@tnode.com> <20160221234244.175a445c@lxorguk.ukuu.org.uk> Message-ID: <07d0ae1e589f95a9aa3972407068a935@tnode.com> User-Agent: Roundcube Webmail Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 21.02.2016 23:42, One Thousand Gnomes wrote: > On Sun, 21 Feb 2016 22:38:29 +0100 > Andrej Krpic wrote: > >> When using n_gsm you have to explicitly set it to work as a >> initiator >> station. This led me to believe that it can also work as a >> responder. snip > This looks reasonable to me. It was never intended to work as a > responder > but it seems clean enough to do so. Have you tested it against some > other > modems with these changes applied ? It has been tested against SIM900 (SIMCom) and M66 (Quectel). > (I'm always wary of patches to this going in without testing on > actual > modems, because the spec is complex and we are not the only ones with > bugs) While second and third patch don't change anything for initiator mode mux, others certainly do. > Also can you please cc these patches to > xinhuix.pan@intel.com This address got rejected. Yours and LKML's didn't. -Andrej