public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: "Carlos Llamas" <cmllamas@google.com>,
	kernel-team@android.com, "Alice Ryhl" <aliceryhl@google.com>,
	"Arve Hjønnevåg" <arve@android.com>,
	"Christian Brauner" <brauner@kernel.org>,
	"Joel Fernandes" <joel@joelfernandes.org>,
	"Martijn Coenen" <maco@android.com>,
	"Suren Baghdasaryan" <surenb@google.com>,
	"Todd Kjos" <tkjos@android.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"Christophe Jaillet" <christophe.jaillet@wanadoo.fr>,
	"John Stultz" <jstultz@google.com>,
	"Nick Chen" <chenjia3@oppo.com>,
	"Steven Moreland" <smoreland@google.com>,
	"Tim Murray" <timmurray@google.com>
Subject: Re: [PATCH v5] binder: use bitmap for faster descriptor lookup
Date: Fri, 14 Jun 2024 11:11:48 +0200	[thread overview]
Message-ID: <2024061443-breeding-obvious-908d@gregkh> (raw)
In-Reply-To: <7daafcb7-2c80-4c2a-bf25-7202634f79f0@web.de>

On Thu, Jun 13, 2024 at 06:50:53PM +0200, Markus Elfring wrote:
> …
> > +++ b/drivers/android/binder.c
> …
> > +static void try_shrink_dmap(struct binder_proc *proc)
> > +{
> …
> > +	binder_proc_lock(proc);
> > +	nbits = dbitmap_shrink_nbits(&proc->dmap);
> > +	binder_proc_unlock(proc);
> …
> > +	new = bitmap_zalloc(nbits, GFP_KERNEL);
> > +	binder_proc_lock(proc);
> > +	dbitmap_shrink(&proc->dmap, new, nbits);
> > +	binder_proc_unlock(proc);
> > +}
> …
> 
> Would you become interested to apply lock guards?
> https://elixir.bootlin.com/linux/v6.10-rc3/source/include/linux/cleanup.h#L124


Hi,

This is the semi-friendly patch-bot of Greg Kroah-Hartman.

Markus, you seem to have sent a nonsensical or otherwise pointless
review comment to a patch submission on a Linux kernel developer mailing
list.  I strongly suggest that you not do this anymore.  Please do not
bother developers who are actively working to produce patches and
features with comments that, in the end, are a waste of time.

Patch submitter, please ignore Markus's suggestion; you do not need to
follow it at all.  The person/bot/AI that sent it is being ignored by
almost all Linux kernel maintainers for having a persistent pattern of
behavior of producing distracting and pointless commentary, and
inability to adapt to feedback.  Please feel free to also ignore emails
from them.

thanks,

greg k-h's patch email bot

      reply	other threads:[~2024-06-14  9:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-16 13:39 [PATCH v3] binder: use bitmap for faster descriptor lookup Carlos Llamas
2024-05-16 14:10 ` Alice Ryhl
2024-05-17  3:24   ` Carlos Llamas
2024-05-17  3:28   ` [PATCH v4] " Carlos Llamas
2024-06-04 14:06     ` Greg Kroah-Hartman
2024-06-06 18:50       ` Carlos Llamas
2024-06-12  4:25       ` [PATCH v5] " Carlos Llamas
2024-06-13 16:50         ` Markus Elfring
2024-06-14  9:11           ` Greg Kroah-Hartman [this message]

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=2024061443-breeding-obvious-908d@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=Markus.Elfring@web.de \
    --cc=aliceryhl@google.com \
    --cc=arve@android.com \
    --cc=brauner@kernel.org \
    --cc=chenjia3@oppo.com \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=cmllamas@google.com \
    --cc=joel@joelfernandes.org \
    --cc=jstultz@google.com \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maco@android.com \
    --cc=smoreland@google.com \
    --cc=surenb@google.com \
    --cc=timmurray@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox