All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sherry Yang <sherryy@android.com>
Cc: linux-kernel@vger.kernel.org, tkjos@google.com, maco@google.com,
	"Arve Hjønnevåg" <arve@android.com>,
	"Riley Andrews" <riandrews@android.com>,
	"open list:ANDROID DRIVERS" <devel@driverdev.osuosl.org>
Subject: Re: [PATCH v2 1/5] android: binder: Refactor prev and next buffer into a helper function
Date: Wed, 23 Aug 2017 16:18:45 -0700	[thread overview]
Message-ID: <20170823231845.GF5193@kroah.com> (raw)
In-Reply-To: <20170823154643.2613-2-sherryy@android.com>

On Wed, Aug 23, 2017 at 08:46:39AM -0700, Sherry Yang wrote:
> Use helper functions buffer_next and buffer_prev instead
> of list_entry to get the next and previous buffers.
> 
> Signed-off-by: Sherry Yang <sherryy@android.com>
> ---
>  drivers/android/binder_alloc.c | 24 +++++++++++++++---------
>  1 file changed, 15 insertions(+), 9 deletions(-)

These all have been acked by the other google/android developers, right?

thanks,

greg k-h

  reply	other threads:[~2017-08-23 23:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-23 15:46 [PATCH v2 0/5] android: binder: move allocator metadata and add shrinker Sherry Yang
2017-08-23 15:46 ` [PATCH v2 1/5] android: binder: Refactor prev and next buffer into a helper function Sherry Yang
2017-08-23 23:18   ` Greg Kroah-Hartman [this message]
2017-08-23 15:46 ` [PATCH v2 2/5] android: binder: Add allocator selftest Sherry Yang
2017-08-23 15:46 ` [PATCH v2 3/5] android: binder: Move buffer out of area shared with user space Sherry Yang
2017-08-24 20:29   ` Dan Carpenter
2017-08-23 15:46 ` [PATCH v2 4/5] android: binder: Add global lru shrinker to binder Sherry Yang
2017-08-23 15:46 ` [PATCH v2 5/5] android: binder: Add shrinker tracepoints Sherry Yang

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=20170823231845.GF5193@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arve@android.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maco@google.com \
    --cc=riandrews@android.com \
    --cc=sherryy@android.com \
    --cc=tkjos@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 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.