From: Johan Hedberg <johan.hedberg@gmail.com>
To: Anderson Lizardo <anderson.lizardo@openbossa.org>
Cc: Vinicius Costa Gomes <vinicius.gomes@openbossa.org>,
linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v3 BlueZ 1/4] gatt: Add support for find included services
Date: Fri, 28 Sep 2012 14:32:12 +0300 [thread overview]
Message-ID: <20120928113212.GA18666@x220> (raw)
In-Reply-To: <CAJdJm_PPjxkXoL+Q=f-3AozUnUErCrD-cQ2KzO1WQSvxJWyRrg@mail.gmail.com>
Hi Lizardo,
On Fri, Sep 28, 2012, Anderson Lizardo wrote:
> On Fri, Sep 28, 2012 at 7:08 AM, Johan Hedberg <johan.hedberg@gmail.com> wrote:
> > Btw, if you guys are wondering why the stricter coding style checks,
> > I've added the following to .git/hooks/pre-{commit,applypatch}:
> >
> > git diff --cached | ~/src/linux/scripts/checkpatch.pl --no-signoff --ignore INITIALISED_STATIC,NEW_TYPEDEFS,VOLATILE --show-types --mailback -
> >
> > You might want to do the same (with the correct path to checkpatch.pl)).
> > And thanks to Luiz for the idea (he's using the same when applying
> > patches).
>
> Thanks for the very useful tip! But which checkpatch.pl version are
> you using? Mine (from bluetooth-next tree) lacks --ignore and
> --show-types options.
I'm using Linus' tree.
Johan
next prev parent reply other threads:[~2012-09-28 11:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 22:33 [PATCH v3 BlueZ 0/4] Support for GATT Find Included Vinicius Costa Gomes
2012-09-24 22:33 ` [PATCH v3 BlueZ 1/4] gatt: Add support for find included services Vinicius Costa Gomes
2012-09-28 11:08 ` Johan Hedberg
2012-09-28 11:28 ` Anderson Lizardo
2012-09-28 11:32 ` Johan Hedberg [this message]
2012-09-24 22:33 ` [PATCH v3 BlueZ 2/4] gatttool: Add "included" command Vinicius Costa Gomes
2012-09-24 22:33 ` [PATCH v3 BlueZ 3/4] core: Add support for included services Vinicius Costa Gomes
2012-09-24 22:33 ` [PATCH v3 BlueZ 4/4] attrib: Remove opcode parameter from g_attrib_send() Vinicius Costa Gomes
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=20120928113212.GA18666@x220 \
--to=johan.hedberg@gmail.com \
--cc=anderson.lizardo@openbossa.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=vinicius.gomes@openbossa.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