From: kuangrufan@iauto.com
To: Todd Kjos <tkjos@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Arve Hjønnevåg" <arve@android.com>,
"Todd Kjos" <tkjos@android.com>,
"Martijn Coenen" <maco@android.com>,
"open list:ANDROID DRIVERS" <devel@driverdev.osuosl.org>
Subject: Re: [PATCH] ANDROID: binder: rename parameter to resolve name collision.
Date: Thu, 31 May 2018 11:15:12 +0800 [thread overview]
Message-ID: <67F0DCCC-BBC5-4B7B-9FC4-1BD83D247DAA@iauto.com> (raw)
In-Reply-To: <CAHRSSEySzqTb-m5Rjv23PuUHi2q4OY485JJjFi1AeLiKL1KJQQ@mail.gmail.com>
> Why is this needed? These don't collide in the namespace:
Sorry, I check it again, you’re right. my bad.
PS:
I need to change the binder API between 32bit & 64bit dynamically.
So I was trying to compile binder as a “.ko”. I compiled the 2
files into the same kernel module, which causes problem.
Best Regards,
> 在 2018年5月30日,下午11:54,Todd Kjos <tkjos@google.com> 写道:
>
> Why is this needed? These don't collide in the namespace:
>
> /sys/module/binder/parameters/debug_mask
>
> and
>
> /sys/module/binder_alloc/parameters/debug_mask.
>
> On Tue, May 29, 2018 at 9:58 PM <kuangrufan@iauto.com> wrote:
> From: Kuang Rufan <kuangrufan@iauto.com>
>
> both bind.c & binder_alloc.c define the same kernel parameter 'debug_mask',
> rename the one in binder_alloc.c to 'alloc_debug_mask'.
>
> Signed-off-by: Kuang Rufan <kuangrufan@iauto.com>
> ---
> drivers/android/binder_alloc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/android/binder_alloc.c b/drivers/android/binder_alloc.c
> index 5a426c877dfb..3850dab493d4 100644
> --- a/drivers/android/binder_alloc.c
> +++ b/drivers/android/binder_alloc.c
> @@ -42,7 +42,7 @@ enum {
> };
> static uint32_t binder_alloc_debug_mask;
>
> -module_param_named(debug_mask, binder_alloc_debug_mask,
> +module_param_named(alloc_debug_mask, binder_alloc_debug_mask,
> uint, 0644);
>
> #define binder_alloc_debug(mask, x...) \
> --
> 2.15.1 (Apple Git-101)
>
prev parent reply other threads:[~2018-05-31 3:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 4:58 kuangrufan
[not found] ` <CAHRSSEySzqTb-m5Rjv23PuUHi2q4OY485JJjFi1AeLiKL1KJQQ@mail.gmail.com>
2018-05-31 3:15 ` kuangrufan [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=67F0DCCC-BBC5-4B7B-9FC4-1BD83D247DAA@iauto.com \
--to=kuangrufan@iauto.com \
--cc=arve@android.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@android.com \
--cc=tkjos@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®