From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: "D. Starke" <daniel.starke@siemens.com>
Cc: linux-serial@vger.kernel.org, gregkh@linuxfoundation.org,
jirislaby@kernel.org, ilpo.jarvinen@linux.intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/9] tty: n_gsm: fix redundant assignment of gsm->encoding
Date: Wed, 5 Apr 2023 11:16:13 +0300 (EEST) [thread overview]
Message-ID: <adf7aae2-2fd8-b191-f37-75185167f418@linux.intel.com> (raw)
In-Reply-To: <20230405054730.3850-1-daniel.starke@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]
On Wed, 5 Apr 2023, D. Starke wrote:
> From: Daniel Starke <daniel.starke@siemens.com>
>
> The function gsmld_open() contains a redundant assignment of gsm->encoding.
> The same value of GSM_ADV_OPT is already assigned to it during the
> initialization of the struct in gsm_alloc_mux() a few lines earlier.
>
> Fix this by removing the redundant second assignment of gsm->encoding in
> gsmld_open().
>
> Fixes: e1eaea46bb40 ("tty: n_gsm line discipline")
> Signed-off-by: Daniel Starke <daniel.starke@siemens.com>
> ---
> drivers/tty/n_gsm.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/tty/n_gsm.c b/drivers/tty/n_gsm.c
> index b7e1369a035c..c42c8b89fd46 100644
> --- a/drivers/tty/n_gsm.c
> +++ b/drivers/tty/n_gsm.c
> @@ -3585,7 +3585,6 @@ static int gsmld_open(struct tty_struct *tty)
> tty->receive_room = 65536;
>
> /* Attach the initial passive connection */
> - gsm->encoding = GSM_ADV_OPT;
> gsmld_attach_gsm(tty, gsm);
>
> /* The mux will not be activated yet, we wait for correct
>
Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
--
i.
prev parent reply other threads:[~2023-04-05 8:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 5:47 [PATCH 1/9] tty: n_gsm: fix redundant assignment of gsm->encoding D. Starke
2023-04-05 5:47 ` [PATCH 2/9] tty: n_gsm: add restart parameter to DLC specific ioctl config D. Starke
2023-04-05 8:15 ` Ilpo Järvinen
2023-04-06 5:17 ` Starke, Daniel
2023-04-05 5:47 ` [PATCH 3/9] tty: n_gsm: add missing description to gsm_config D. Starke
2023-04-05 8:18 ` Ilpo Järvinen
2023-04-06 5:26 ` Starke, Daniel
2023-04-05 5:47 ` [PATCH 4/9] tty: n_gsm: fix unneeded initialization of ret in gsm_dlci_config D. Starke
2023-04-05 8:23 ` Ilpo Järvinen
2023-04-06 5:31 ` Starke, Daniel
2023-04-05 5:47 ` [PATCH 5/9] tty: n_gsm: add open_error counter to gsm_mux D. Starke
2023-04-05 8:41 ` Ilpo Järvinen
2023-04-06 5:42 ` Starke, Daniel
2023-04-05 5:47 ` [PATCH 6/9] tty: n_gsm: increase malformed counter for malformed control frames D. Starke
2023-04-05 8:44 ` Ilpo Järvinen
2023-04-06 5:45 ` Starke, Daniel
2023-04-05 5:47 ` [PATCH 7/9] tty: n_gsm: increase gsm_mux unsupported counted where appropriate D. Starke
2023-04-05 9:00 ` Ilpo Järvinen
2023-04-06 5:57 ` Starke, Daniel
2023-04-05 5:47 ` [PATCH 8/9] tty: n_gsm: add DLCI specific rx/tx statistics D. Starke
2023-04-05 9:13 ` Ilpo Järvinen
2023-04-06 6:02 ` Starke, Daniel
2023-04-05 5:47 ` [PATCH 9/9] tty: n_gsm: cleanup gsm_control_command and gsm_control_reply D. Starke
2023-04-05 9:15 ` Ilpo Järvinen
2023-04-06 6:04 ` Starke, Daniel
2023-04-05 8:16 ` Ilpo Järvinen [this message]
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=adf7aae2-2fd8-b191-f37-75185167f418@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=daniel.starke@siemens.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
/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