public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Xingrui Yi <yixingrui@linux.alibaba.com>
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] vt: remove old FONT ioctls definitions in uapi
Date: Thu, 28 Jul 2022 10:26:10 +0200	[thread overview]
Message-ID: <YuJIIl/LwGwuYdib@kroah.com> (raw)
In-Reply-To: <20220722061133.7765-1-yixingrui@linux.alibaba.com>

On Fri, Jul 22, 2022 at 02:11:33PM +0800, Xingrui Yi wrote:
> As was demonstrated by commit ff2047fb755d ("vt: drop old FONT ioctls"),
> old font ioctls like PIO_FONT have been deleted and KDFONTOP ioctl is used
> for years instead.
> 
> However, unused definitions of these ioctl numbers and "strut
> consolefontdesc" still exist in a uapi header. They could have been removed
> since no userspace was using them. Otherwise they will become a
> misleading for users, and users will fail with ENOTTY with wrong call.
> 
> We are moving old font ioctl numbers definitions here to guide users to
> use KDFONTOP.
> 
> Signed-off-by: Xingrui Yi <yixingrui@linux.alibaba.com>
> ---
>  include/uapi/linux/kd.h | 13 -------------
>  1 file changed, 13 deletions(-)
> 
> diff --git a/include/uapi/linux/kd.h b/include/uapi/linux/kd.h
> index ee929ece4112..d739b17fc942 100644
> --- a/include/uapi/linux/kd.h
> +++ b/include/uapi/linux/kd.h
> @@ -6,19 +6,6 @@
>  
>  /* 0x4B is 'K', to avoid collision with termios and vt */
>  
> -#define GIO_FONT	0x4B60	/* gets font in expanded form */
> -#define PIO_FONT	0x4B61	/* use font in expanded form */
> -
> -#define GIO_FONTX	0x4B6B	/* get font using struct consolefontdesc */
> -#define PIO_FONTX	0x4B6C	/* set font using struct consolefontdesc */
> -struct consolefontdesc {
> -	unsigned short charcount;	/* characters in font (256 or 512) */
> -	unsigned short charheight;	/* scan lines per character (1-32) */
> -	char __user *chardata;		/* font data in expanded form */
> -};
> -
> -#define PIO_FONTRESET   0x4B6D	/* reset to default font */
> -
>  #define GIO_CMAP	0x4B70	/* gets colour palette on VGA+ */
>  #define PIO_CMAP	0x4B71	/* sets colour palette on VGA+ */
>  

Did you rebuild a distribution like Debian to verify that these values
and structure are not used anywhere?

thanks,

greg k-h

  reply	other threads:[~2022-07-28  8:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-22  6:11 [PATCH] vt: remove old FONT ioctls definitions in uapi Xingrui Yi
2022-07-28  8:26 ` Greg KH [this message]
2022-07-29 21:21   ` Adam Borowski
2022-07-30 12:00     ` Greg KH

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=YuJIIl/LwGwuYdib@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=yixingrui@linux.alibaba.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