From: Florian Grandel <fgrandel@gmail.com>
To: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Review patches
Date: Wed, 08 Apr 2015 22:55:27 +0200 [thread overview]
Message-ID: <552595BF.9080704@gmail.com> (raw)
Hi!
Is there anything I can do to improve my patches or make it easier for
you to review them? Is there anything obvious that's wrong with them? If
it's just that you don't have time then: no worries. Just wanted to make
sure I wasn't missing anything. As these are my first patches I'm unsure
whether I'm following the right process.
Thanks!
Florian
reply other threads:[~2015-04-08 20:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=552595BF.9080704@gmail.com \
--to=fgrandel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.