From: Johan Hedberg <johan.hedberg@gmail.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, padovan@profusion.mobi,
marcel@holtmann.org, Fabio Estevam <fabio.estevam@freescale.com>
Subject: Re: [PATCH] net: bluetooth: Fix 'enable_hs' type
Date: Wed, 11 Jan 2012 00:48:05 +0200 [thread overview]
Message-ID: <20120110224804.GA10526@x220.ger.corp.intel.com> (raw)
In-Reply-To: <CAOMZO5ANrmCNZep0-5OJ9gKzvDBrCdqfU91o81f_2FjSjXnAHw@mail.gmail.com>
Hi Fabio,
On Tue, Jan 10, 2012, Fabio Estevam wrote:
> Hi Johan,
>
> On Tue, Jan 10, 2012 at 7:31 PM, Johan Hedberg <johan.hedberg@gmail.com> wrote:
> > Hi Fabio,
> >
> > On Tue, Jan 10, 2012, Fabio Estevam wrote:
> >> > The patch has been applied to my bluetooth-next tree. Don't you get the
> >> > same warning for enable_mgmt and enable_le as well? Those seem to be
> >> > declared in a similar manner.
> >>
> >> No, because enable_mgmt and enable_le are already declared as 'bool'.
> >
> > I don't know what tree you're looking at but at least in mine they're
> > both "static int".
>
> I am using linux-next. Please check:
>
> http://git.kernel.org/?p=linux%2Fkernel%2Fgit%2Fnext%2Flinux-next-history.git&a=search&h=refs%2Fheads%2Fmaster&st=grep&s=enable_mgmt
Yep, seems commit eb939922 from Rusty Russel took care of this, but the
commit has not yet made it to the bluetooth-next tree.
Johan
prev parent reply other threads:[~2012-01-10 22:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 20:33 [PATCH] net: bluetooth: Fix 'enable_hs' type Fabio Estevam
2012-01-10 20:44 ` Marcel Holtmann
2012-01-10 21:00 ` Johan Hedberg
2012-01-10 21:08 ` Fabio Estevam
2012-01-10 21:31 ` Johan Hedberg
2012-01-10 22:21 ` Fabio Estevam
2012-01-10 22:48 ` Johan Hedberg [this message]
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=20120110224804.GA10526@x220.ger.corp.intel.com \
--to=johan.hedberg@gmail.com \
--cc=fabio.estevam@freescale.com \
--cc=festevam@gmail.com \
--cc=linux-bluetooth@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