Linux bluetooth development
 help / color / mirror / Atom feed
From: Gustavo Padovan <gustavo@padovan.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Johan Hedberg <johan.hedberg@gmail.com>,
	Tedd Ho-Jeong An <tedd.an@intel.com>,
	linux-bluetooth <linux-bluetooth@vger.kernel.org>,
	don.fry@intel.com
Subject: Re: [RFC] Bluetooth: Add support for Intel Bluetooth device [8087:07dc]
Date: Thu, 11 Apr 2013 16:35:52 -0300	[thread overview]
Message-ID: <20130411193552.GA28775@joana> (raw)
In-Reply-To: <5C338FDA-422A-4600-8DCF-43065D3EB6EA@holtmann.org>

Hi Marcel,

* Marcel Holtmann <marcel@holtmann.org> [2013-04-10 15:09:55 -0700]:

> Hi Johan,
> 
> >>> +	const u8		*patch_curr;
> >>> +	char			pfile[32];
> >>> +	u8			*m_off_code;
> >>> +
> >>> +	u8 m_on[] = { 0x01, 0x00 };
> >>> +	u8 m_off_1[] = { 0x00, 0x01 };
> >>> +	u8 m_off_2[] = { 0x00, 0x02 };
> >> 
> >> Shouldn't this be __u8. Johan, any preference. I know that I used __u8
> >> for the bcm92035 vendor command.
> > 
> > To my understanding __u8 (and __u16 and __u32 too) are intended for code
> > that's to be shared with user space (e.g. our upcoming uapi header
> > file(s)). Anything else should just use u8. At least this is what I
> > discovered after some research when I get more heavily involved with
> > kernel development a few years ago.
> 
> then you might have to tweak my other patch a little to fix this for BCM92035 setup routine.

I fixed up your patch on bluetooth-next. I didn't see this comment here before
applying the patch.

	Gustavo

  reply	other threads:[~2013-04-11 19:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-10  2:44 [RFC] Bluetooth: Add support for Intel Bluetooth device [8087:07dc] Tedd Ho-Jeong An
2013-04-10 15:40 ` Fry, Don
2013-04-10 16:23   ` Tedd Ho-Jeong An
2013-04-10 16:11 ` Marcel Holtmann
2013-04-10 16:34   ` Tedd Ho-Jeong An
2013-04-10 22:04   ` Johan Hedberg
2013-04-10 22:09     ` Marcel Holtmann
2013-04-11 19:35       ` Gustavo Padovan [this message]
2013-04-10 23:57   ` 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=20130411193552.GA28775@joana \
    --to=gustavo@padovan.org \
    --cc=don.fry@intel.com \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=tedd.an@intel.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