From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: qca_vkondrat@qca.qualcomm.com, linux-wireless@vger.kernel.org,
wil6210@qca.qualcomm.com,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
linux-next@vger.kernel.org
Subject: Re: [PATCH next] drivers/net/wireless/ath/wil6210/debugfs.c: Use 'uint64_t' instead of 'cycles_t' to avoid warnings
Date: Wed, 24 Dec 2014 23:22:05 +0800 [thread overview]
Message-ID: <549ADA1D.8030509@gmail.com> (raw)
In-Reply-To: <8761d19j6z.fsf@kamboji.qca.qualcomm.com>
On 12/24/2014 11:11 PM, Kalle Valo wrote:
> Chen Gang <gang.chen.5i5j@gmail.com> writes:
>
>> Oh, sorry, I forgot the word wrap (after change a new pc). I shall send
>> patch v2 for it.
>
> While at it, could you also please simplify the title. You don't have to
> put the full directory there, it just makes it more difficult to read.
> This should be enough:
>
> wil6210: Use 'uint64_t' instead of 'cycles_t' to avoid warnings
>
Oh, I have sent patch v2, if necessary, I will send patch v3 for it.
(if necessary, please let me know)
> I see quite a few patches with titles like 'drivers: net: wireless: ath:
> fix foo'. Where an earth is that coming from? Bad documentation
> somewhere?
>
I guess, this can let the patch makers have a easier life, e.g. for me,
I may send patches for various sub-systems (arch/*, drivers/*, net/*,
also another projects ...).
Thanks.
--
Chen Gang
Open, share, and attitude like air, water, and life which God blessed
next prev parent reply other threads:[~2014-12-24 15:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-24 14:40 [PATCH next] drivers/net/wireless/ath/wil6210/debugfs.c: Use 'uint64_t' instead of 'cycles_t' to avoid warnings Chen Gang
2014-12-24 15:01 ` Chen Gang
[not found] ` <549AD54F.3020605-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-12-24 15:11 ` Kalle Valo
2014-12-24 15:22 ` Chen Gang [this message]
2014-12-24 15:35 ` Kalle Valo
2014-12-24 15:54 ` Chen Gang
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=549ADA1D.8030509@gmail.com \
--to=gang.chen.5i5j@gmail.com \
--cc=kvalo@codeaurora.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=qca_vkondrat@qca.qualcomm.com \
--cc=wil6210@qca.qualcomm.com \
/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).