From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Carlos Llamas <cmllamas@google.com>
Cc: "Arve Hjønnevåg" <arve@android.com>,
"Todd Kjos" <tkjos@android.com>,
"Martijn Coenen" <maco@android.com>,
"Joel Fernandes" <joel@joelfernandes.org>,
"Christian Brauner" <brauner@kernel.org>,
"Suren Baghdasaryan" <surenb@google.com>,
"Nathan Chancellor" <nathan@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
kernel-team@android.com, linux-kernel@vger.kernel.org,
"Colin Ian King" <colin.i.king@intel.com>,
"kernel test robot" <lkp@intel.com>,
"Nick Desaulniers" <ndesaulniers@google.com>,
"Bill Wendling" <morbo@google.com>,
"Justin Stitt" <justinstitt@google.com>
Subject: Re: [PATCH v2] binder: remove redundant variable page_addr
Date: Thu, 7 Mar 2024 21:43:46 +0000 [thread overview]
Message-ID: <2024030733-granny-octagon-7cfc@gregkh> (raw)
In-Reply-To: <20240116193235.184666-1-cmllamas@google.com>
On Tue, Jan 16, 2024 at 07:32:34PM +0000, Carlos Llamas wrote:
> From: Colin Ian King <colin.i.king@intel.com>
>
> Variable page_addr is being assigned a value that is never read. The
> variable is redundant and can be removed.
>
> Cleans up clang scan build warning:
> warning: Value stored to 'page_addr' is never read [deadcode.DeadStores]
>
> Signed-off-by: Colin Ian King <colin.i.king@intel.com>
> Fixes: 162c79731448 ("binder: avoid user addresses in debug logs")
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202312060851.cudv98wG-lkp@intel.com/
> Acked-by: Carlos Llamas <cmllamas@google.com>
> ---
>
> Notes:
> v2: added tags, used char-misc-next as base
>
> drivers/android/binder_alloc.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/android/binder_alloc.c b/drivers/android/binder_alloc.c
> index a4a4dc87ba53..34d7a1494bc7 100644
> --- a/drivers/android/binder_alloc.c
> +++ b/drivers/android/binder_alloc.c
> @@ -925,7 +925,6 @@ void binder_alloc_deferred_release(struct binder_alloc *alloc)
> int i;
>
> for (i = 0; i < alloc->buffer_size / PAGE_SIZE; i++) {
> - unsigned long page_addr;
> bool on_lru;
>
> if (!alloc->pages[i].page_ptr)
> @@ -933,7 +932,6 @@ void binder_alloc_deferred_release(struct binder_alloc *alloc)
>
> on_lru = list_lru_del(&binder_freelist,
> &alloc->pages[i].lru);
> - page_addr = alloc->buffer + i * PAGE_SIZE;
> binder_alloc_debug(BINDER_DEBUG_BUFFER_ALLOC,
> "%s: %d: page %d %s\n",
> __func__, alloc->pid, i,
>
> base-commit: 5850edccec30325707f953bc088497b3b9041231
> --
> 2.43.0.275.g3460e3d667-goog
>
This doesn't apply to my tree anymore, can you rebase?
thanks,
greg k-h
next prev parent reply other threads:[~2024-03-07 21:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <https://lore.kernel.org/all/ZZl_-XGd-WJ0juz9@google.com/>
2024-01-16 19:32 ` [PATCH v2] binder: remove redundant variable page_addr Carlos Llamas
2024-03-07 21:43 ` Greg Kroah-Hartman [this message]
2024-03-07 22:15 ` [PATCH v3] " 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=2024030733-granny-octagon-7cfc@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=aliceryhl@google.com \
--cc=arve@android.com \
--cc=brauner@kernel.org \
--cc=cmllamas@google.com \
--cc=colin.i.king@intel.com \
--cc=joel@joelfernandes.org \
--cc=justinstitt@google.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=maco@android.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=surenb@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