From: Jiri Slaby <jirislaby@kernel.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Andrew J. Kroll" <ag784@freenet.buffalo.edu>,
processes-Sapan Bhatia <sapan@corewars.org>
Subject: Re: [PATCH v2 1/1] tty: n_tty: Fix some misdocumented functions
Date: Thu, 27 May 2021 08:30:04 +0200 [thread overview]
Message-ID: <3c8f2e14-f0a7-409f-e17e-ff7d94b48566@kernel.org> (raw)
In-Reply-To: <20210526083125.549626-1-lee.jones@linaro.org>
On 26. 05. 21, 10:31, Lee Jones wrote:
> Fixes the following W=1 kernel build warning(s):
>
> drivers/tty/n_tty.c:623: warning: expecting prototype for process_echoes(). Prototype was for __process_echoes() instead
> drivers/tty/n_tty.c:1109: warning: expecting prototype for isig(). Prototype was for __isig() instead
> drivers/tty/n_tty.c:1268: warning: expecting prototype for n_tty_receive_char(). Prototype was for n_tty_receive_char_special() instead
> drivers/tty/n_tty.c:2132: warning: Excess function parameter 'buf' description in 'n_tty_read'
>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Jiri Slaby <jirislaby@kernel.org>
> Cc: "Andrew J. Kroll" <ag784@freenet.buffalo.edu>
> Cc: processes-Sapan Bhatia <sapan@corewars.org>
> Signed-off-by: Lee Jones <lee.jones@linaro.org>
> ---
>
> v2: Rebased
>
> drivers/tty/n_tty.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/tty/n_tty.c b/drivers/tty/n_tty.c
> index 0ec93f1a61f5d..56d3b43d8a3a4 100644
> --- a/drivers/tty/n_tty.c
> +++ b/drivers/tty/n_tty.c
...
> @@ -1248,7 +1248,7 @@ n_tty_receive_signal_char(struct tty_struct *tty, int signal, unsigned char c)
> }
>
> /**
> - * n_tty_receive_char - perform processing
> + * n_tty_receive_char_special - perform processing
No, please move the doc to the function in this case instead.
> * @tty: terminal device
> * @c: character
> *
> @@ -2042,11 +2042,11 @@ static int job_control(struct tty_struct *tty, struct file *file)
> }
>
>
> -/**
> +/*
Why this?
> * n_tty_read - read function for tty
> * @tty: tty device
> * @file: file object
> - * @buf: userspace buffer pointer
> + * @kbuf: userspace buffer pointer
> * @nr: size of I/O
> *
> * Perform reads for the line discipline. We are guaranteed that the
>
thanks,
--
js
suse labs
next prev parent reply other threads:[~2021-05-27 6:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 8:31 [PATCH v2 1/1] tty: n_tty: Fix some misdocumented functions Lee Jones
2021-05-27 6:30 ` Jiri Slaby [this message]
2021-05-27 8:20 ` Lee Jones
2021-05-27 9:23 ` 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=3c8f2e14-f0a7-409f-e17e-ff7d94b48566@kernel.org \
--to=jirislaby@kernel.org \
--cc=ag784@freenet.buffalo.edu \
--cc=gregkh@linuxfoundation.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sapan@corewars.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