From: Marcel Holtmann <marcel@holtmann.org>
To: Suraj Sumangala <suraj@atheros.com>
Cc: Suraj Sumangala <Suraj.Sumangala@Atheros.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
Jothikumar Mothilal <Jothikumar.Mothilal@Atheros.com>
Subject: Re: [PATCH v3] hciattach application support for Atheros AR300x Bluetooth Chip
Date: Fri, 21 May 2010 09:34:53 +0200 [thread overview]
Message-ID: <1274427293.27220.31.camel@localhost.localdomain> (raw)
In-Reply-To: <4BF613AF.2080303@atheros.com>
Hi Suraj,
> >> Implements support for Atheros AR300x Bluetooth chip in hciattach.
> >> Adds feature to bring up AR300x Bluetooth chip
> >> with and without enhanced power management enabled.
> >>
> >> Signed-off-by: Suraj <suraj@Atheros.com>
> >
> > not SOBs for BlueZ userspace. That is kernel only.
> >
> >> ---
> >> Makefile.tools | 1 +
> >> tools/hciattach.8 | 6 +
> >> tools/hciattach.c | 111 +++++
> >> tools/hciattach.h | 3 +
> >> tools/hciattach_ar3k.c | 1223 ++++++++++++++++++++++++++++++++++++++++++++++++
> >> 5 files changed, 1344 insertions(+), 0 deletions(-)
> >> create mode 100755 tools/hciattach_ar3k.c
> >
> > While hciattach is kinda the bad sheep inside BlueZ, I will enforce the
> > general coding style for it for all new contributions. So could you
> > please fix that one first. Otherwise it makes no sense for me to go
> > through such a big patch if I have to complain about the coding style
> > breakage for every second line. A general rule is if it fails
> > check-patch.pl from the kernel, then you are doing something wrong.
>
> I had verified this patch using checkpatch and it did not complain. I
> had also verified it manually according to the comments others have
> given previously for different patches.
>
> If you still see issues, then we can add that check too to checkpatch if
> possible.
then maybe checkpatch.pl is not good enough for this. I see way too many
empty lines, weird if breakages, and many more. So as I said, this needs
cleanup first.
Regards
Marcel
next prev parent reply other threads:[~2010-05-21 7:34 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 5:01 [PATCH] Added support for Atheros AR300x Bluetooth Chip suraj
2010-03-24 5:27 ` suraj
2010-03-29 9:01 ` suraj
[not found] ` <1271673889.19858.4.camel@atheros013-desktop>
2010-04-19 18:11 ` Support " Luis R. Rodriguez
2010-03-31 10:59 ` [PATCH] Added Host level support for Atheros AR3xxx " suraj
2010-04-19 23:53 ` [PATCH] Added support for Atheros AR300x " Gustavo F. Padovan
2010-04-20 10:20 ` [PATCH v3] " suraj
2010-04-20 15:36 ` Gustavo F. Padovan
2010-04-20 17:34 ` Luis R. Rodriguez
2010-04-21 4:21 ` Suraj Sumangala
2010-04-21 10:22 ` [PATCH v4] Add support for the " suraj
2010-04-21 17:30 ` Luis R. Rodriguez
2010-04-22 6:10 ` Gustavo F. Padovan
2010-04-22 6:54 ` Suraj Sumangala
2010-04-22 8:59 ` Gustavo F. Padovan
2010-04-22 9:10 ` [PATCH v5] " suraj
2010-04-26 11:00 ` suraj
2010-04-27 6:19 ` [PATCH] New Firmware for Atheros bluetooth chipset AR3011 suraj
2010-04-27 8:28 ` [PATCH] patch to request new firmware for AR3011 Chip suraj
2010-04-27 15:55 ` Luis R. Rodriguez
2010-05-11 9:04 ` [PATCH v2] ath3k: add support for new firmware suraj
2010-05-05 12:33 ` [PATCH v5] Add support for the Atheros AR300x Bluetooth Chip suraj
2010-05-06 7:45 ` buffer starvation with multiple ACL link suraj
2010-05-20 16:02 ` Marcel Holtmann
2010-05-10 20:12 ` [PATCH v5] Add support for the Atheros AR300x Bluetooth Chip Luis R. Rodriguez
2010-05-11 8:29 ` suraj
2010-05-18 11:39 ` suraj
2010-05-12 13:47 ` [PATCH v3] hciattach application support for " suraj
2010-05-20 13:37 ` suraj
2010-05-20 16:00 ` Marcel Holtmann
2010-05-21 5:01 ` Suraj Sumangala
2010-05-21 7:34 ` Marcel Holtmann [this message]
2010-05-20 16:09 ` [PATCH v5] Add support for the " Marcel Holtmann
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=1274427293.27220.31.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=Jothikumar.Mothilal@Atheros.com \
--cc=Luis.Rodriguez@Atheros.com \
--cc=Suraj.Sumangala@Atheros.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=suraj@atheros.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;
as well as URLs for NNTP newsgroup(s).