[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2024070439-expanse-usual-434f@gregkh>
Date: Thu, 4 Jul 2024 15:00:07 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Yu-Ting Tseng <yutingtseng@...gle.com>
Cc: cmllamas@...gle.com, tkjos@...gle.com, arve@...roid.com,
maco@...roid.com, joel@...lfernandes.org, brauner@...nel.org,
surenb@...gle.com, aliceryhl@...gle.com, kernel-team@...roid.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v6 0/2] binder: frozen notification
On Wed, Jul 03, 2024 at 10:58:42AM -0700, Yu-Ting Tseng wrote:
> Separated the binder_features change into its own patch.
>
> Yu-Ting Tseng (2):
> binder: frozen notification
> binder: frozen notification binder_features flag
>
> drivers/android/binder.c | 284 +++++++++++++++++-
> drivers/android/binder_internal.h | 21 +-
> drivers/android/binderfs.c | 8 +
> include/uapi/linux/android/binder.h | 36 +++
> .../filesystems/binderfs/binderfs_test.c | 1 +
> 5 files changed, 346 insertions(+), 4 deletions(-)
>
>
> base-commit: 14d7c92f8df9c0964ae6f8b813c1b3ac38120825
This email thread is crazy, sorry, look at how it shows up in sane email
clients:
https://lore.kernel.org/all/20240703175843.3639568-2-yutingtseng@google.com/
Please just send a new series, as it's own thread, so we can figure out
what to do here.
And for some reason I have 2 different copies of the v6 series, one sent
to the list, and one not, which makes no sense either. For that reason
alone I can't take this :(
Please, realize what this looks like from a reviewer's point of view,
you want to make it simple and easy for us to know what to do...
Please fix up and send a v7.
thanks,
greg k-h
Powered by blists - more mailing lists