mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@kernel.org>
To: Tom Rix <trix@redhat.com>, gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tty: define hung_up_tty_compat_ioctl with CONFIG_COMPAT
Date: Tue, 2 May 2023 07:02:03 +0200	[thread overview]
Message-ID: <67eeec7d-a114-07e0-de56-08a63d91af58@kernel.org> (raw)
In-Reply-To: <20230501025602.2905173-1-trix@redhat.com>

On 01. 05. 23, 4:56, Tom Rix wrote:
> gcc reports
> drivers/tty/tty_io.c:446:13: error: ‘hung_up_tty_compat_ioctl’
>    defined but not used [-Werror=unused-function]
>    446 | static long hung_up_tty_compat_ioctl(struct file *file,
>        |             ^~~~~~~~~~~~~~~~~~~~~~~~
> 
> hung_up_tty_compat_ioctl is used conditionally with CONFIG_COMPAT,
> so it should be likewise defined.



> Signed-off-by: Tom Rix <trix@redhat.com>
> ---
>   drivers/tty/tty_io.c | 2 ++
>   1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/tty/tty_io.c b/drivers/tty/tty_io.c
> index 553182753098..7fe404d56ce7 100644
> --- a/drivers/tty/tty_io.c
> +++ b/drivers/tty/tty_io.c
> @@ -443,11 +443,13 @@ static long hung_up_tty_ioctl(struct file *file, unsigned int cmd,
>   	return cmd == TIOCSPGRP ? -ENOTTY : -EIO;
>   }
>   
> +#ifdef CONFIG_COMPAT
>   static long hung_up_tty_compat_ioctl(struct file *file,
>   				     unsigned int cmd, unsigned long arg)
>   {
>   	return cmd == TIOCSPGRP ? -ENOTTY : -EIO;
>   }
> +#endif
>   
>   static int hung_up_tty_fasync(int fd, struct file *file, int on)
>   {

Hi,

Arnd sent a better fix already:
https://lore.kernel.org/all/20230429203523.538756-1-arnd@kernel.org/

thanks,
-- 
js
suse labs


      reply	other threads:[~2023-05-02  5:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-01  2:56 Tom Rix
2023-05-02  5:02 ` Jiri Slaby [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=67eeec7d-a114-07e0-de56-08a63d91af58@kernel.org \
    --to=jirislaby@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trix@redhat.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

all inboxes | Powered by JetHome®