public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Yu-Ting Tseng <yutingtseng@google.com>
Cc: cmllamas@google.com, tkjos@google.com, arve@android.com,
	maco@android.com, joel@joelfernandes.org, brauner@kernel.org,
	surenb@google.com, aliceryhl@google.com, kernel-team@android.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/2] binder: frozen notification
Date: Thu, 4 Jul 2024 15:00:07 +0200	[thread overview]
Message-ID: <2024070439-expanse-usual-434f@gregkh> (raw)
In-Reply-To: <20240703175843.3639568-2-yutingtseng@google.com>

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

  reply	other threads:[~2024-07-04 13:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240618221347.106627-1-yutingtseng@google.com>
2024-06-22  3:16 ` [PATCH v2] binder: frozen notification Yu-Ting Tseng
2024-06-22  3:16 ` Yu-Ting Tseng
2024-06-24 14:24   ` Alice Ryhl
2024-06-24 15:50     ` Yu-Ting Tseng
2024-06-24 15:53       ` Carlos Llamas
2024-06-24 15:56         ` Yu-Ting Tseng
2024-06-24 17:20           ` [PATCH v3] " Yu-Ting Tseng
2024-06-25  3:01             ` Yu-Ting Tseng
2024-06-24 17:20           ` [PATCH v3 1/1] " Yu-Ting Tseng
2024-06-28 18:42             ` Carlos Llamas
2024-07-01 18:23           ` [PATCH v4] " Yu-Ting Tseng
2024-07-01 18:27           ` Yu-Ting Tseng
2024-07-03  4:18             ` Carlos Llamas
2024-07-03 17:08           ` [PATCH v5] " Yu-Ting Tseng
2024-07-03 17:08           ` Yu-Ting Tseng
2024-07-03 17:58           ` [PATCH v6 0/2] " Yu-Ting Tseng
2024-07-04 13:00             ` Greg KH [this message]
2024-07-03 17:58           ` [PATCH v6 1/2] " Yu-Ting Tseng
2024-07-03 17:58           ` [PATCH v6 2/2] binder: frozen notification binder_features flag Yu-Ting Tseng
2024-06-24 15:10   ` [PATCH v2] binder: frozen notification Carlos Llamas

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=2024070439-expanse-usual-434f@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=aliceryhl@google.com \
    --cc=arve@android.com \
    --cc=brauner@kernel.org \
    --cc=cmllamas@google.com \
    --cc=joel@joelfernandes.org \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maco@android.com \
    --cc=surenb@google.com \
    --cc=tkjos@google.com \
    --cc=yutingtseng@google.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