From: Tim Gardner <tim.gardner@canonical.com>
To: Luciano Coelho <coelho@ti.com>
Cc: linux-kernel@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
Eliad Peller <eliad@wizery.com>, Arik Nemtsov <arik@wizery.com>,
Eyal Shapira <eyal@wizery.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 3.6-rc3] wlcore: Declare MODULE_FIRMWARE usage
Date: Wed, 29 Aug 2012 11:13:31 -0600 [thread overview]
Message-ID: <503E4DBB.4030606@canonical.com> (raw)
In-Reply-To: <1346259706.3935.2.camel@cumari.coelho.fi>
On 08/29/2012 11:01 AM, Luciano Coelho wrote:
> On Wed, 2012-08-29 at 08:48 -0600, Tim Gardner wrote:
>> Cc: Luciano Coelho <coelho@ti.com>
>> Cc: "John W. Linville" <linville@tuxdriver.com>
>> Cc: Eliad Peller <eliad@wizery.com>
>> Cc: Arik Nemtsov <arik@wizery.com>
>> Cc: Eyal Shapira <eyal@wizery.com>
>> Cc: linux-wireless@vger.kernel.org
>> Cc: netdev@vger.kernel.org
>> Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
>> ---
>
> Please add a proper commit message. And there's no need to put all
> these people in Cc: in the commit log. CC'ing when sending the patch is
> enough (even though for such small patch, the linux-wireless mailing
> list and myself is enough).
>
> --
> Luca.
>
What more would you like covered in the commit message that isn't
obvious from the subject?
The Cc list comes from scripts/get_maintainers.pl as suggested by
Documentation/SubmittingPatches: "5) Select e-mail destination."
rtg
--
Tim Gardner tim.gardner@canonical.com
next prev parent reply other threads:[~2012-08-29 17:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 14:48 [PATCH 3.6-rc3] wlcore: Declare MODULE_FIRMWARE usage Tim Gardner
2012-08-29 17:01 ` Luciano Coelho
2012-08-29 17:13 ` Tim Gardner [this message]
2012-08-29 18:57 ` Luciano Coelho
2012-08-29 19:09 ` [PATCH 3.6-rc3 v2] " Tim Gardner
2012-09-28 8:49 ` Luciano Coelho
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=503E4DBB.4030606@canonical.com \
--to=tim.gardner@canonical.com \
--cc=arik@wizery.com \
--cc=coelho@ti.com \
--cc=eliad@wizery.com \
--cc=eyal@wizery.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).