From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Gleb Fotengauer-Malinovskiy <glebfm@altlinux.org>
Cc: Aleksa Sarai <asarai@suse.de>,
David Laight <David.Laight@ACULAB.COM>,
James Hogan <james.hogan@imgtec.com>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>,
Valentin Rothberg <vrothberg@suse.com>,
"linux-parisc@vger.kernel.org" <linux-parisc@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
"linux-xtensa@linux-xtensa.org" <linux-xtensa@linux-xtensa.org>,
"linux-alpha@vger.kernel.org" <linux-alpha@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Dmitry V. Levin" <ldv@altlinux.org>,
Jiri Slaby <jslaby@suse.com>,
"sparclinux@vger.kernel.org" <sparclinux@vger.kernel.org>,
Christian Brauner <christian.brauner@ubuntu.com>
Subject: Re: [PATCH] [PING] Fix TIOCGPTPEER ioctl definition
Date: Mon, 17 Jul 2017 15:47:46 +0200 [thread overview]
Message-ID: <20170717134746.GA19574@kroah.com> (raw)
In-Reply-To: <20170717132946.GK21910@glebfm.cloud.tilaa.com>
On Mon, Jul 17, 2017 at 04:29:46PM +0300, Gleb Fotengauer-Malinovskiy wrote:
> This ioctl does nothing to justify an _IOC_READ or _IOC_WRITE flag
> because it doesn't copy anything from/to userspace to access the
> argument.
>
> Fixes: 54ebbfb16034 ("tty: add TIOCGPTPEER ioctl")
> Signed-off-by: Gleb Fotengauer-Malinovskiy <glebfm@altlinux.org>
> Acked-by: Aleksa Sarai <asarai@suse.de>
> Acked-by: Arnd Bergmann <arnd@arndb.de>
Why the PING? -rc1 just happened, so I am only now able to apply the
patch to the tree. Please relax, you are behind about 800+ other
patches in my queue...
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Gleb Fotengauer-Malinovskiy <glebfm@altlinux.org>
Cc: Aleksa Sarai <asarai@suse.de>,
David Laight <David.Laight@ACULAB.COM>,
James Hogan <james.hogan@imgtec.com>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>,
Valentin Rothberg <vrothberg@suse.com>,
"linux-parisc@vger.kernel.org" <linux-parisc@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
"linux-xtensa@linux-xtensa.org" <linux-xtensa@linux-xtensa.org>,
"linux-alpha@vger.kernel.org" <linux-alpha@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Dmitry V. Levin" <ldv@altlinux.org>,
Jiri Slaby <jslaby@suse.com>,
"sparclinux@vger.kernel.org" <sparclinux@vger.kernel.org>,
Christian Brauner <christian.brauner@ubuntu.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH] [PING] Fix TIOCGPTPEER ioctl definition
Date: Mon, 17 Jul 2017 15:47:46 +0200 [thread overview]
Message-ID: <20170717134746.GA19574@kroah.com> (raw)
Message-ID: <20170717134746.IJaR-EkWrJjA7kw0FfBaT4-1veJ5bIxRMfagiWQasgw@z> (raw)
In-Reply-To: <20170717132946.GK21910@glebfm.cloud.tilaa.com>
On Mon, Jul 17, 2017 at 04:29:46PM +0300, Gleb Fotengauer-Malinovskiy wrote:
> This ioctl does nothing to justify an _IOC_READ or _IOC_WRITE flag
> because it doesn't copy anything from/to userspace to access the
> argument.
>
> Fixes: 54ebbfb16034 ("tty: add TIOCGPTPEER ioctl")
> Signed-off-by: Gleb Fotengauer-Malinovskiy <glebfm@altlinux.org>
> Acked-by: Aleksa Sarai <asarai@suse.de>
> Acked-by: Arnd Bergmann <arnd@arndb.de>
Why the PING? -rc1 just happened, so I am only now able to apply the
patch to the tree. Please relax, you are behind about 800+ other
patches in my queue...
thanks,
greg k-h
next prev parent reply other threads:[~2017-07-17 13:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 13:29 [PATCH] [PING] Fix TIOCGPTPEER ioctl definition Gleb Fotengauer-Malinovskiy
2017-07-17 13:29 ` Gleb Fotengauer-Malinovskiy
2017-07-17 13:47 ` Greg Kroah-Hartman [this message]
2017-07-17 13:47 ` Greg Kroah-Hartman
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=20170717134746.GA19574@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=David.Laight@ACULAB.COM \
--cc=arnd@arndb.de \
--cc=asarai@suse.de \
--cc=christian.brauner@ubuntu.com \
--cc=glebfm@altlinux.org \
--cc=james.hogan@imgtec.com \
--cc=jslaby@suse.com \
--cc=ldv@altlinux.org \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=sparclinux@vger.kernel.org \
--cc=vrothberg@suse.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