From: Jeff Cook <jeff@deserettechnology.com>
To: Anderson Lizardo <anderson.lizardo@openbossa.org>, gustavo@padovan.org
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: Add support for BCM20702A0 [0b05, 17b5]
Date: Thu, 25 Oct 2012 13:17:02 -0600 [thread overview]
Message-ID: <5089902E.9020204@deserettechnology.com> (raw)
In-Reply-To: <CAJdJm_NrmfU17aQDmO0hbihV673Of0iFnLqk4=-sPh=g44eixA@mail.gmail.com>
On 10/24/2012 06:20 AM, Anderson Lizardo wrote:
> Hi Jeff,
>
> On Wed, Oct 24, 2012 at 5:29 AM, Jeff Cook <jeff@deserettechnology.com> wrote:
>> Hello all,
>>
>> Please see included patch. First-time submitter so let me know if I did
>> something wrong.
>
> Just one more suggestion (adding to Gustavo's comments), you may want to read:
>
> http://www.kernel.org/doc/Documentation/SubmittingPatches
>
> Specially sections 12 and 15.
Thanks for the help everyone. I did skim SubmittingPatches prior to
submission, but dropped off before sections 12 and 15; the information
seemed outdated since it made no mention of git by the time I stopped
reading (around section 9 or so), so I looked elsewhere.
I will resubmit according to the information in Section 15. Do I need to
add something like "try 2" to the patch's subject line, or is it okay
without that?
next prev parent reply other threads:[~2012-10-25 19:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 9:29 [PATCH] Bluetooth: Add support for BCM20702A0 [0b05, 17b5] Jeff Cook
2012-10-24 12:11 ` Gustavo Padovan
2012-10-24 12:20 ` Anderson Lizardo
2012-10-25 19:17 ` Jeff Cook [this message]
2012-10-26 12:49 ` Anderson Lizardo
2012-10-27 11:01 ` Jeff Cook
2012-10-31 18:15 ` Gustavo Padovan
2012-11-09 23:39 ` [PATCHv2] " Jeff Cook
2012-11-19 21:41 ` Gustavo Padovan
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=5089902E.9020204@deserettechnology.com \
--to=jeff@deserettechnology.com \
--cc=anderson.lizardo@openbossa.org \
--cc=gustavo@padovan.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.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;
as well as URLs for NNTP newsgroup(s).