mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@kernel.org>
To: "D. Starke" <daniel.starke@siemens.com>,
	linux-serial@vger.kernel.org, gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/6] tty: n_gsm: introduce gsm_control_command() function
Date: Tue, 30 Aug 2022 08:59:36 +0200	[thread overview]
Message-ID: <fe014b7b-a1d2-9be9-625b-2f630934c56c@kernel.org> (raw)
In-Reply-To: <20220823062259.4754-4-daniel.starke@siemens.com>

On 23. 08. 22, 8:22, D. Starke wrote:
> From: Daniel Starke <daniel.starke@siemens.com>
> 
> Move the content of gsm_control_transmit() to a new function
> gsm_control_command() with a more generic signature and analog to
> gsm_control_reply(). Use this within gsm_control_transmit().
> 
> This is needed to simplify upcoming functional additions.
> 
> Signed-off-by: Daniel Starke <daniel.starke@siemens.com>
> ---
>   drivers/tty/n_gsm.c | 30 +++++++++++++++++++++++-------
>   1 file changed, 23 insertions(+), 7 deletions(-)
> 
> No changes since v1.
> 
> diff --git a/drivers/tty/n_gsm.c b/drivers/tty/n_gsm.c
> index 9535e84f3063..5a20561c0a5d 100644
> --- a/drivers/tty/n_gsm.c
> +++ b/drivers/tty/n_gsm.c
> @@ -1316,6 +1316,28 @@ static void gsm_dlci_data_kick(struct gsm_dlci *dlci)
>    */
>   
>   
> +/**
> + *	gsm_control_command	-	send a command frame to a control
> + *	@gsm: gsm channel
> + *	@cmd: the command to use
> + *	@data: data to follow encoded info
> + *	@dlen: length of data
> + *
> + *	Encode up and queue a UI/UIH frame containing our command.

These tabs after asterisks are not understood by kernel-doc. You should 
add no new ones.

> + */
> +static int gsm_control_command(struct gsm_mux *gsm, int cmd, u8 *data, int dlen)

Can gsm and data be const? I assume gsm cannot due to call to 
gsm_data_queue(). And what about cmd & dlen being uint? cmd seems to be 
u8 at least...

> +{
> +	struct gsm_msg *msg = gsm_data_alloc(gsm, 0, dlen + 2, gsm->ftype);
> +
> +	if (msg == NULL)
> +		return -ENOMEM;

\n here

> +	msg->data[0] = (cmd << 1) | CR | EA;	/* Set C/R */
> +	msg->data[1] = (dlen << 1) | EA;
> +	memcpy(msg->data + 2, data, dlen);
> +	gsm_data_queue(gsm->dlci[0], msg);

\n here

> +	return 0;
> +}
> +
>   /**
>    *	gsm_control_reply	-	send a response frame to a control
>    *	@gsm: gsm channel
> @@ -1623,13 +1645,7 @@ static void gsm_control_response(struct gsm_mux *gsm, unsigned int command,
>   
>   static void gsm_control_transmit(struct gsm_mux *gsm, struct gsm_control *ctrl)
>   {
> -	struct gsm_msg *msg = gsm_data_alloc(gsm, 0, ctrl->len + 2, gsm->ftype);
> -	if (msg == NULL)
> -		return;
> -	msg->data[0] = (ctrl->cmd << 1) | CR | EA;	/* command */
> -	msg->data[1] = (ctrl->len << 1) | EA;
> -	memcpy(msg->data + 2, ctrl->data, ctrl->len);
> -	gsm_data_queue(gsm->dlci[0], msg);
> +	gsm_control_command(gsm, ctrl->cmd, ctrl->data, ctrl->len);
>   }

thanks,
-- 
js
suse labs


  reply	other threads:[~2022-08-30  6:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-23  6:22 [PATCH v2 1/6] tty: n_gsm: add enumeration for gsm encodings D. Starke
2022-08-23  6:22 ` [PATCH v2 2/6] tty: n_gsm: name gsm tty device minors D. Starke
2022-08-30  6:49   ` Jiri Slaby
2022-08-23  6:22 ` [PATCH v2 3/6] tty: n_gsm: replace use of gsm_read_ea() with gsm_read_ea_val() D. Starke
2022-08-30  6:55   ` Jiri Slaby
2022-08-23  6:22 ` [PATCH v2 4/6] tty: n_gsm: introduce gsm_control_command() function D. Starke
2022-08-30  6:59   ` Jiri Slaby [this message]
2022-08-23  6:22 ` [PATCH v2 5/6] tty: n_gsm: name the debug bits D. Starke
2022-08-30  7:00   ` Jiri Slaby
2022-08-23  6:22 ` [PATCH v2 6/6] tty: n_gsm: add debug bit for user payload D. Starke
2022-08-30  6:49 ` [PATCH v2 1/6] tty: n_gsm: add enumeration for gsm encodings Jiri Slaby

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=fe014b7b-a1d2-9be9-625b-2f630934c56c@kernel.org \
    --to=jirislaby@kernel.org \
    --cc=daniel.starke@siemens.com \
    --cc=gregkh@linuxfoundation.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

all inboxes | Powered by JetHome®