From: Souptick Joarder <jrdr.linux@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: arve@android.com, tkjos@android.com, maco@android.com,
christian@brauner.io, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: android: vsoc: Remove VSOC_WAIT_FOR_INCOMING_INTERRUPT
Date: Mon, 11 Feb 2019 21:21:19 +0530 [thread overview]
Message-ID: <CAFqt6zYh2qxBKyOCH3xZmS_Jq5nU+nZyLhbmGOey4Y-VAk+ZoQ@mail.gmail.com> (raw)
In-Reply-To: <20190211154044.GA16105@kroah.com>
On Mon, Feb 11, 2019 at 9:10 PM Greg KH <gregkh@linuxfoundation.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@gmail.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.
next prev parent reply other threads:[~2019-02-11 15:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 15:26 [PATCH] staging: android: vsoc: Remove VSOC_WAIT_FOR_INCOMING_INTERRUPT Souptick Joarder
2019-02-11 15:40 ` Greg KH
2019-02-11 15:51 ` Souptick Joarder [this message]
2019-02-11 15:57 ` Greg KH
2019-02-11 16:45 ` Souptick Joarder
2019-02-11 17:11 ` Greg KH
2019-02-11 17:22 ` Todd Kjos
2019-02-11 18:57 ` Alistair Strachan
2019-02-12 13:12 ` Souptick Joarder
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=CAFqt6zYh2qxBKyOCH3xZmS_Jq5nU+nZyLhbmGOey4Y-VAk+ZoQ@mail.gmail.com \
--to=jrdr.linux@gmail.com \
--cc=arve@android.com \
--cc=christian@brauner.io \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@android.com \
--cc=tkjos@android.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.