[PATCH] tidspbridge: Rename module from bridgedriver to tidspbridge

[PATCH] tidspbridge: Rename module from bridgedriver to tidspbridge

[Joe Perches]

tidspbridge when built as a module is named bridgedriver.

bridgedriver is not a particularly good module name.

tidspbridge is what the source is named.  That seems
a more appropriate module name too as it describes
the hardware function better.

Signed-off-by: Joe Perches <joe@perches.com>
---
 drivers/staging/tidspbridge/Makefile |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/staging/tidspbridge/Makefile b/drivers/staging/tidspbridge/Makefile
index fd6a276..8c8c92a 100644
--- a/drivers/staging/tidspbridge/Makefile
+++ b/drivers/staging/tidspbridge/Makefile
@@ -1,4 +1,4 @@
-obj-$(CONFIG_TIDSPBRIDGE)	+= bridgedriver.o
+obj-$(CONFIG_TIDSPBRIDGE)	+= tidspbridge.o
 
 libgen = gen/gh.o gen/uuidutil.o
 libcore = core/chnl_sm.o core/msg_sm.o core/io_sm.o core/tiomap3430.o \
@@ -13,7 +13,7 @@ libdload = dynload/cload.o dynload/getsection.o dynload/reloc.o \
 		 dynload/tramp.o
 libhw = hw/hw_mmu.o
 
-bridgedriver-y := $(libgen) $(libservices) $(libcore) $(libpmgr) $(librmgr) \
+tidspbridge-y := $(libgen) $(libservices) $(libcore) $(libpmgr) $(librmgr) \
 			$(libdload) $(libhw)
 
 #Machine dependent

Re: [PATCH] tidspbridge: Rename module from bridgedriver to tidspbridge

[Ramirez Luna, Omar]

On Tue, Jan 24, 2012 at 3:25 PM, Joe Perches <joe@perches.com> wrote:
> tidspbridge when built as a module is named bridgedriver.
>
> bridgedriver is not a particularly good module name.
>
> tidspbridge is what the source is named.  That seems
> a more appropriate module name too as it describes
> the hardware function better.
>
> Signed-off-by: Joe Perches <joe@perches.com>
> ---
>  drivers/staging/tidspbridge/Makefile |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/tidspbridge/Makefile b/drivers/staging/tidspbridge/Makefile
> index fd6a276..8c8c92a 100644
> --- a/drivers/staging/tidspbridge/Makefile
> +++ b/drivers/staging/tidspbridge/Makefile
> @@ -1,4 +1,4 @@
> -obj-$(CONFIG_TIDSPBRIDGE)      += bridgedriver.o
> +obj-$(CONFIG_TIDSPBRIDGE)      += tidspbridge.o
>
>  libgen = gen/gh.o gen/uuidutil.o
>  libcore = core/chnl_sm.o core/msg_sm.o core/io_sm.o core/tiomap3430.o \
> @@ -13,7 +13,7 @@ libdload = dynload/cload.o dynload/getsection.o dynload/reloc.o \
>                 dynload/tramp.o
>  libhw = hw/hw_mmu.o
>
> -bridgedriver-y := $(libgen) $(libservices) $(libcore) $(libpmgr) $(librmgr) \
> +tidspbridge-y := $(libgen) $(libservices) $(libcore) $(libpmgr) $(librmgr) \
>                        $(libdload) $(libhw)
>
>  #Machine dependent
>
>

Sound good to me, and unless there is an objection, it also gives
plenty of time for the change to be noticed.

Regards,

Omar
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH] tidspbridge: Rename module from bridgedriver to tidspbridge

[Felipe Contreras]

On Mon, Jan 30, 2012 at 7:34 PM, Ramirez Luna, Omar <omar.ramirez@ti.com> wrote:
> On Tue, Jan 24, 2012 at 3:25 PM, Joe Perches <joe@perches.com> wrote:
>> tidspbridge when built as a module is named bridgedriver.
>>
>> bridgedriver is not a particularly good module name.
>>
>> tidspbridge is what the source is named.  That seems
>> a more appropriate module name too as it describes
>> the hardware function better.
>>
>> Signed-off-by: Joe Perches <joe@perches.com>
>> ---
>>  drivers/staging/tidspbridge/Makefile |    4 ++--
>>  1 files changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/staging/tidspbridge/Makefile b/drivers/staging/tidspbridge/Makefile
>> index fd6a276..8c8c92a 100644
>> --- a/drivers/staging/tidspbridge/Makefile
>> +++ b/drivers/staging/tidspbridge/Makefile
>> @@ -1,4 +1,4 @@
>> -obj-$(CONFIG_TIDSPBRIDGE)      += bridgedriver.o
>> +obj-$(CONFIG_TIDSPBRIDGE)      += tidspbridge.o
>>
>>  libgen = gen/gh.o gen/uuidutil.o
>>  libcore = core/chnl_sm.o core/msg_sm.o core/io_sm.o core/tiomap3430.o \
>> @@ -13,7 +13,7 @@ libdload = dynload/cload.o dynload/getsection.o dynload/reloc.o \
>>                 dynload/tramp.o
>>  libhw = hw/hw_mmu.o
>>
>> -bridgedriver-y := $(libgen) $(libservices) $(libcore) $(libpmgr) $(librmgr) \
>> +tidspbridge-y := $(libgen) $(libservices) $(libcore) $(libpmgr) $(librmgr) \
>>                        $(libdload) $(libhw)
>>
>>  #Machine dependent
>>
>>
>
> Sound good to me, and unless there is an objection, it also gives
> plenty of time for the change to be noticed.

Yeah, I agree. I also have thought on doing this.

-- 
Felipe Contreras

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel