From: "Gustavo F. Padovan" <gustavo@las.ic.unicamp.br>
To: linux-bluetooth@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] Bluetooth: l2cap clean ups
Date: Mon, 20 Apr 2009 01:31:04 -0300 [thread overview]
Message-ID: <1240201868-1396-1-git-send-email-gustavo@las.ic.unicamp.br> (raw)
Hi,
These patches are result of my hackings to l2cap.
First and third just create macros to do not show some number in
code. Also facilite the hacking because we don't need to go to spec
to figure out what that numbers shows. The first patch is a resend.
The last patch is the result of run l2cap files against checkpatch.pl
Regards
next reply other threads:[~2009-04-20 4:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 4:31 Gustavo F. Padovan [this message]
2009-04-20 4:31 ` [PATCH 1/4] Bluetooth: create macros for channels identifiers Gustavo F. Padovan
2009-04-20 4:31 ` [PATCH 2/4] Bluetooth: remove unnecessary atribution to err var Gustavo F. Padovan
2009-04-20 4:31 ` [PATCH 3/4] Bluetooth: create macro to hint mask on receiving config request Gustavo F. Padovan
2009-04-20 4:31 ` [PATCH 4/4] Bluetooth: fix many errors and warnings reported by checkpatch.pl Gustavo F. Padovan
2009-04-20 5:20 ` [PATCH 0/4] Bluetooth: l2cap clean ups 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=1240201868-1396-1-git-send-email-gustavo@las.ic.unicamp.br \
--to=gustavo@las.ic.unicamp.br \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@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