Linux bluetooth development
 help / color / mirror / Atom feed
From: Gordon <kernel@gkr.i24.cc>
To: Johan Hedberg <johan.hedberg@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: PATCH hid2hci for CSR 8510 A10
Date: Fri, 28 Mar 2014 21:23:58 +0100	[thread overview]
Message-ID: <1396038238.5349.11.camel@g-VPCF13Z1E> (raw)
In-Reply-To: <20140328194907.GA24300@t440s.P-661HNU-F1>

Hi Johan,

On Fr, 2014-03-28 at 21:49 +0200, Johan Hedberg wrote:
> Hi Gordon,
> 
> On Fri, Mar 28, 2014, Gordon wrote:
> > some time ago I sent a patch attached to following mail.
> > 
> > On Mo, 2013-12-30 at 22:59 +0100, Gordon wrote:
> > > Hi,
> > > 
> > > Could someone please review.
> > 
> > I didn't get a reply yet. Since it has been my first mail to this list I
> > wonder whether there is anything wrong with this request, or just nobody
> > is interested ?
> 
> A couple of things regarding the presentation of the patch should at
> least be fixed:
> 
>  - Send it as a proper git patch, i.e. using git commit, format-patch
>    and send-email

ok, will try.

>  - Try to follow the bluez.git coding style which is roughly the same as
>    the Linux kernel coding style. I realize the rest of hid2hci.c is
>    probably the worst reference for good BlueZ coding style (being one
>    of the oldest pieces of code with very little maintenance over the
>    years).
> 

thanks for the detailed remarks, although removed from the reply, I will
address them.

> > +		//unable to detect EALREADY
> 
> We don't generally use C++ style comments in the tree. Prefer /* .. */
> where possible. In this case I'd elaborate the comment a bit since I
> don't quite understand what it means.

I am not sure, other functions in hid2hci presumably return this when
the device is already in the mode that should be switched to. 

> 
> > +	case HID:
> > +		// currently unknown what to do here
> 

the method for switching back to hid mode is unknown, should I remove
the cases or just be more verbose in the comments ?

Thanks,

Gordon


  reply	other threads:[~2014-03-28 20:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-30 21:59 PATCH hid2hci for CSR 8510 A10 Gordon
2014-03-28 19:21 ` Gordon
2014-03-28 19:49   ` Johan Hedberg
2014-03-28 20:23     ` Gordon [this message]
2014-03-29 11:37     ` Gordon
2014-03-29 11:37       ` [PATCH] hid2hci add CSR 8510 A10 support Gordon
2014-03-31 12:17         ` Anderson Lizardo
2014-04-01 21:38           ` [PATCH v3] " Gordon
2015-01-07  8:24             ` Gordon
2015-01-07  9:12               ` Johan Hedberg
2015-01-07 10:10                 ` [PATCH v4] " kernel
2015-01-07 20:31                   ` Johan Hedberg
2015-01-07 20:52                     ` Gordon
2015-01-07 21:21                     ` Gordon
2015-01-07 22:03                     ` [PATCH v5 0/2] " kernel
2015-01-07 22:03                       ` [PATCH v5 1/2] " kernel
2015-01-07 22:04                       ` [PATCH v5 2/2] use const uint_8* for pointer in control_message kernel
2015-01-08 10:02                       ` [PATCH v5 0/2] hid2hci add CSR 8510 A10 support Johan Hedberg

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=1396038238.5349.11.camel@g-VPCF13Z1E \
    --to=kernel@gkr.i24.cc \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /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