Linux-fbdev Archive mirror
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@kernel.org>
To: "Jiri Slaby" <jirislaby@kernel.org>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Alexey Gladkov" <legion@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	kbd@lists.linux.dev, linux-api@vger.kernel.org,
	linux-fbdev@vger.kernel.org, linux-serial@vger.kernel.org,
	"Alexander Viro" <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH v5 1/3] VT: Use macros to define ioctls
Date: Wed, 29 May 2024 09:44:04 +0200	[thread overview]
Message-ID: <b779241d-36d8-4728-a126-9340bc569a2d@app.fastmail.com> (raw)
In-Reply-To: <0da9785e-ba44-4718-9d08-4e96c1ba7ab2@kernel.org>

On Wed, May 29, 2024, at 09:29, Jiri Slaby wrote:
> On 18. 04. 24, 8:18, Greg Kroah-Hartman wrote:
>> 
>> This is a nice cleanup, thanks for doing it, I'll just take this one
>> change now if you don't object.
>
> Unfortunately, _IOC_NONE is 1 on some archs as noted by Arnd, and this 
> commit changed the kd ioctl values in there which broke stuff as noted 
> by Al.
>
> We either:
> * use _IOC(0, X, Y) in here, instead of _IO(X, Y), or
> * define KDIOC(X) as _IOC(0, KD_IOCTL_BASE, X), or
> * revert the commit which landed to -rc1 already.

I would prefer a simple revert, as the other options may
end up more confusing. Another option might be a new
global macro, if we then go an convert all plain ioctl
command numbers to that.

      Arnd

  reply	other threads:[~2024-05-29  7:44 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1708960303.git.legion@kernel.org>
2024-03-12 14:23 ` [PATCH v3 0/2] VT: Add ability to get font requirements legion
2024-03-12 14:23   ` [PATCH v3 1/2] VT: Add KDFONTINFO ioctl legion
2024-03-15  9:15     ` Helge Deller
2024-03-12 14:23   ` [PATCH v3 2/2] VT: Allow to get max font width and height legion
2024-03-13 17:40     ` Oleg Bulatov
2024-04-02 11:09       ` Jiri Slaby
2024-03-15  9:16     ` Helge Deller
2024-04-02 10:32   ` [RESEND PATCH v3 0/2] VT: Add ability to get font requirements Alexey Gladkov
2024-04-02 10:32     ` [RESEND PATCH v3 1/2] VT: Add KDFONTINFO ioctl Alexey Gladkov
2024-04-02 11:02       ` Jiri Slaby
2024-04-02 13:19         ` Alexey Gladkov
2024-04-03  5:27           ` Jiri Slaby
2024-04-10 16:29             ` Alexey Gladkov
2024-04-10 17:11               ` Greg Kroah-Hartman
2024-04-02 17:50         ` [PATCH v4 0/3] VT: Add ability to get font requirements Alexey Gladkov
2024-04-02 17:50           ` [PATCH v4 1/3] VT: Use macros to define ioctls Alexey Gladkov
2024-04-02 17:50           ` [PATCH v4 2/3] VT: Add KDFONTINFO ioctl Alexey Gladkov
2024-04-03  4:55             ` Greg Kroah-Hartman
2024-04-03  5:05             ` Jiri Slaby
2024-04-10 16:36               ` Alexey Gladkov
2024-04-11  3:53                 ` Jiri Slaby
2024-04-02 17:50           ` [PATCH v4 3/3] VT: Allow to get max font width and height Alexey Gladkov
2024-04-17 17:37           ` [PATCH v5 0/3] VT: Add ability to get font requirements Alexey Gladkov
2024-04-17 17:37             ` [PATCH v5 1/3] VT: Use macros to define ioctls Alexey Gladkov
2024-04-18  6:18               ` Greg Kroah-Hartman
2024-05-29  7:29                 ` Jiri Slaby
2024-05-29  7:44                   ` Arnd Bergmann [this message]
2024-05-29  8:44                   ` Al Viro
2024-04-17 17:37             ` [PATCH v5 2/3] VT: Add KDFONTINFO ioctl Alexey Gladkov
2024-04-17 19:31               ` Helge Deller
2024-04-18 10:45                 ` Alexey Gladkov
2024-04-25 10:33                   ` Helge Deller
2024-04-25 11:06                     ` Alexey Gladkov
2024-04-25 11:35                       ` Helge Deller
2024-04-18  6:18               ` Greg Kroah-Hartman
2024-04-18 10:27                 ` Alexey Gladkov
2024-04-17 17:37             ` [PATCH v5 3/3] VT: Allow to get max font width and height Alexey Gladkov
2024-04-02 10:32     ` [RESEND PATCH v3 2/2] " Alexey Gladkov

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=b779241d-36d8-4728-a126-9340bc569a2d@app.fastmail.com \
    --to=arnd@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=kbd@lists.linux.dev \
    --cc=legion@kernel.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).