From: pavan_savoy@ti.com
To: gregkh@suse.de, linux-kernel@vger.kernel.org
Cc: padovan@profusion.mobi, marcel@holtmann.org,
linux-bluetooth@vger.kernel.org, Pavan Savoy <pavan_savoy@ti.com>
Subject: [PATCH 0/2] keep ti-st staging updated
Date: Tue, 14 Dec 2010 06:06:38 -0600 [thread overview]
Message-ID: <1292328400-7649-1-git-send-email-pavan_savoy@ti.com> (raw)
From: Pavan Savoy <pavan_savoy@ti.com>
Greg,
In my attempt to upstream BT driver based on TI ST driver,
I had posted several patches to linux-bluetooth.
At this point, there are no review comments as such specifically
to bluetooth driver but there are few concerns regarding the TI-ST driver itself.
As I await the responses from Gustavo, Marcel on how best to proceed
in improving btwilink driver, I am deleting the very old bt_drv from
the staging and updating it with relatively acceptable btwilink driver.
Pavan Savoy (2):
drivers:staging: ti-st: remove bt_drv
drivers:staging: ti-st: update the TI ST BT driver
drivers/staging/ti-st/Kconfig | 25 +-
drivers/staging/ti-st/Makefile | 6 +-
drivers/staging/ti-st/bt_drv.c | 509 --------------------------------------
drivers/staging/ti-st/bt_drv.h | 61 -----
drivers/staging/ti-st/btwilink.c | 363 +++++++++++++++++++++++++++
drivers/staging/ti-st/sysfs-uim | 28 --
6 files changed, 376 insertions(+), 616 deletions(-)
delete mode 100644 drivers/staging/ti-st/bt_drv.c
delete mode 100644 drivers/staging/ti-st/bt_drv.h
create mode 100644 drivers/staging/ti-st/btwilink.c
delete mode 100644 drivers/staging/ti-st/sysfs-uim
next reply other threads:[~2010-12-14 12:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 12:06 pavan_savoy [this message]
2010-12-14 12:06 ` [PATCH 1/2] drivers:staging: ti-st: remove bt_drv pavan_savoy
2010-12-14 12:06 ` [PATCH 2/2] drivers:staging: ti-st: update the TI ST BT driver pavan_savoy
2010-12-16 20:24 ` [PATCH 1/2] drivers:staging: ti-st: remove bt_drv Greg KH
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=1292328400-7649-1-git-send-email-pavan_savoy@ti.com \
--to=pavan_savoy@ti.com \
--cc=gregkh@suse.de \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=padovan@profusion.mobi \
/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®