From: Jiri Slaby <jirislaby@kernel.org>
To: Zhenguo Zhao <zhenguo6858@gmail.com>, gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tty: n_gsm: delete SABM command frame as requester
Date: Thu, 1 Jul 2021 08:13:25 +0200 [thread overview]
Message-ID: <695b2537-28e0-90c4-d516-727dfeead12d@kernel.org> (raw)
In-Reply-To: <1625108078-16491-1-git-send-email-zhenguo6858@gmail.com>
On 01. 07. 21, 4:54, Zhenguo Zhao wrote:
> From: Zhenguo Zhao <Zhenguo.Zhao1@unisoc.com>
>
> as initiator,it need to send SABM conmmand ,as requester,there is
> no need to send the SABM control frame,it will cause redundant data.
Hi,
is there any document you can refer to? I am still confused so I don't
understand why this didn't matter until now. Maybe you only need to
explain better the whole point behind the introduced initiator/requester
functionality.
In any way, could you use spell checker on the commit log (like "conmmand")?
> Signed-off-by: Zhenguo Zhao <Zhenguo.Zhao1@unisoc.com>
> ---
> drivers/tty/n_gsm.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/tty/n_gsm.c b/drivers/tty/n_gsm.c
> index 5fea02c..e66418b 100644
> --- a/drivers/tty/n_gsm.c
> +++ b/drivers/tty/n_gsm.c
> @@ -3005,8 +3005,9 @@ static int gsmtty_open(struct tty_struct *tty, struct file *filp)
> /* We could in theory open and close before we wait - eg if we get
> a DM straight back. This is ok as that will have caused a hangup */
> tty_port_set_initialized(port, 1);
> - /* Start sending off SABM messages */
> - gsm_dlci_begin_open(dlci);
> + /* Start sending off SABM messages for initiator */
> + if (gsm->initiator)
> + gsm_dlci_begin_open(dlci);
> /* And wait for virtual carrier */
> return tty_port_block_til_ready(port, tty, filp);
> }
>
thanks,
--
js
suse labs
next prev parent reply other threads:[~2021-07-01 6:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 2:54 [PATCH] tty: n_gsm: delete SABM command frame as requester Zhenguo Zhao
2021-07-01 6:13 ` Jiri Slaby [this message]
2021-07-01 6:15 ` Jiri Slaby
[not found] ` <CAGGV+3+Oc415RJGueGHdYnDGWFqyuD_6ehBWybhR=6bDoFE9Wg@mail.gmail.com>
[not found] ` <CAGGV+3J9Kj-GoiCBYNN=JLx=Jj02yMkpdg5E_+3W-tvQ_jESyQ@mail.gmail.com>
[not found] ` <CAGGV+3JT6P=tM3_t045FfJtZQ_diPv2_qmnE1LHYvkQo7J7MAw@mail.gmail.com>
[not found] ` <CAGGV+3LHqgpuvWC_WpkqYnk=U_1vaCReEMrYkenDSAi95740hQ@mail.gmail.com>
2021-07-07 5:53 ` Greg KH
2021-07-01 8:00 ` kernel test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=695b2537-28e0-90c4-d516-727dfeead12d@kernel.org \
--to=jirislaby@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zhenguo6858@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox