From: Marcel Holtmann <marcel@holtmann.org>
To: "Gustavo F. Padovan" <padovan@profusion.mobi>
Cc: pavan_savoy@ti.com, linux-bluetooth@vger.kernel.org,
greg@kroah.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] drivers:bluetooth: TI_ST bluetooth driver
Date: Fri, 08 Oct 2010 10:37:42 +0200 [thread overview]
Message-ID: <1286527062.6145.182.camel@aeonflux> (raw)
In-Reply-To: <20101007184534.GB13602@vigoh>
Hi Gustavo,
> Change the commit subject to "Bluetooth: TI_ST bluetooth driver"
>
> * pavan_savoy@ti.com <pavan_savoy@ti.com> [2010-10-07 14:47:16 -0400]:
>
> > From: Pavan Savoy <pavan_savoy@ti.com>
> >
> > This is the bluetooth protocol driver for the TI WiLink7 chipsets.
> > Texas Instrument's WiLink chipsets combine wireless technologies
> > like BT, FM, GPS and WLAN onto a single chip.
> >
> > This Bluetooth driver works on top of the TI_ST shared transport
> > line discipline driver which also allows other drivers like
> > FM V4L2 and GPS character driver to make use of the same UART interface.
> >
> > Signed-off-by: Pavan Savoy <pavan_savoy@ti.com>
> > ---
> > drivers/bluetooth/bt_ti.c | 489 +++++++++++++++++++++++++++++++++++++++++++++
> > 1 files changed, 489 insertions(+), 0 deletions(-)
> > create mode 100644 drivers/bluetooth/bt_ti.c
>
> We don't have filename with bt_.. in drivers/bluetooth/. Maybe ti_st.c
> should be a better name, or something like that.
actually we have the bt prefix for company generic ones where they
didn't wanna use the hardware name.
So I prefer to use the hardware for a driver since it is much more clear
that way. You acronym naming here is bad. It is confusing like hell.
What about just calling this btwilink.c or something. I just spinning
ideas here.
Regards
Marcel
next prev parent reply other threads:[~2010-10-08 8:37 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 18:47 [PATCH 0/2] v2: Bluetooth driver for TI_ST pavan_savoy
2010-10-07 18:47 ` [PATCH 1/2] drivers:bluetooth: TI_ST bluetooth driver pavan_savoy
2010-10-07 18:45 ` Gustavo F. Padovan
2010-10-07 21:53 ` Savoy, Pavan
2010-10-07 21:53 ` Savoy, Pavan
2010-10-08 8:37 ` Marcel Holtmann [this message]
2010-10-08 14:54 ` Savoy, Pavan
2010-10-08 14:54 ` Savoy, Pavan
2010-10-07 18:47 ` [PATCH 2/2] drivers:bluetooth: Kconfig & Makefile for TI BT pavan_savoy
2010-10-07 18:47 ` Gustavo F. Padovan
-- strict thread matches above, loose matches on Subject: below --
2010-10-06 22:34 [PATCH 0/2] Bluetooth driver for TI WiLink 7 pavan-savoy
2010-10-06 22:34 ` [PATCH 1/2] drivers:bluetooth: TI_ST bluetooth driver pavan-savoy
2010-10-07 10:05 ` Marcel Holtmann
2010-10-07 14:34 ` Greg KH
2010-10-07 15:21 ` Marcel Holtmann
2010-10-07 15:35 ` Greg KH
2010-10-07 17:57 ` Gustavo F. Padovan
2010-10-07 21:24 ` Savoy, Pavan
2010-10-07 21:24 ` Savoy, Pavan
2010-10-07 17:51 ` Gustavo F. Padovan
2010-10-07 21:30 ` Greg KH
2010-10-07 19:09 ` Gustavo F. Padovan
2010-10-07 22:17 ` Greg KH
2010-10-07 19:44 ` Gustavo F. Padovan
2010-10-07 14:59 ` Savoy, Pavan
2010-10-07 14:59 ` Savoy, Pavan
2010-10-07 15:17 ` Marcel Holtmann
2010-10-07 15:23 ` Savoy, Pavan
2010-10-07 15:23 ` Savoy, Pavan
2010-10-07 15:37 ` Marcel Holtmann
2010-10-07 15:47 ` Savoy, Pavan
2010-10-07 15:47 ` Savoy, Pavan
2010-10-07 15:49 ` Marcel Holtmann
2010-10-07 15:52 ` Savoy, Pavan
2010-10-07 15:52 ` Savoy, Pavan
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=1286527062.6145.182.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=greg@kroah.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=padovan@profusion.mobi \
--cc=pavan_savoy@ti.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.