[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFqt6zYTkUwU144+pzoLz7kcjQz=j9vQ-H2NLthA_3hOzCBfdw@mail.gmail.com>
Date: Mon, 11 Feb 2019 22:15:18 +0530
From: Souptick Joarder <jrdr.linux@...il.com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: devel@...verdev.osuosl.org, tkjos@...roid.com,
linux-kernel@...r.kernel.org, arve@...roid.com, maco@...roid.com,
christian@...uner.io
Subject: Re: [PATCH] staging: android: vsoc: Remove VSOC_WAIT_FOR_INCOMING_INTERRUPT
On Mon, Feb 11, 2019 at 9:27 PM Greg KH <gregkh@...uxfoundation.org> wrote:
>
> On Mon, Feb 11, 2019 at 09:21:19PM +0530, Souptick Joarder wrote:
> > On Mon, Feb 11, 2019 at 9:10 PM Greg KH <gregkh@...uxfoundation.org> wrote:
> > >
> > > On Mon, Feb 11, 2019 at 08:56:02PM +0530, Souptick Joarder wrote:
> > > > As mentioned in TODO list, Removed VSOC_WAIT_FOR_INCOMING_INTERRUPT
> > > > ioctl. This functionality has been superseded by the futex and is
> > > > there for legacy reasons.
> > > >
> > > > Signed-off-by: Souptick Joarder <jrdr.linux@...il.com>
> > > > ---
> > > > drivers/staging/android/uapi/vsoc_shm.h | 7 -------
> > > > drivers/staging/android/vsoc.c | 5 -----
> > > > 2 files changed, 12 deletions(-)
> > >
> > > So userspace is all fixed up now and this ioctl can be dropped? Any
> > > pointers to the userspace commit that did this?
> >
> > I am not sure about user space part.
>
> Then we can not just delete the ioctl :)
Agree, but where to verify the user space commit ?
Any pointer to the source code path ?
Powered by blists - more mailing lists