From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: [PATCH] ath10k: unify warning messages in mac.c
Date: Tue, 11 Mar 2014 13:16:46 +0200 [thread overview]
Message-ID: <87k3c1gf35.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <8761nv44nd.fsf@kamboji.qca.qualcomm.com> (Kalle Valo's message of "Mon, 3 Mar 2014 18:40:22 +0200")
Kalle Valo <kvalo@qca.qualcomm.com> writes:
>> I think we should agree on one of the two approaches:
>>
>> a) start with a verb:
>>
>> "failed to add peer %pM on vdev %i: %d"
>> "failed to initialize dfs pattern detector"
>> "timed out while waiting for scan completion"
>>
>> b) start with a noun:
>>
>> "peer %pM on vdev %i could not be added: %d"
>> "dfs pattern detector could not initialize"
>> "scan timed out"
>>
>> These are still mixed.
>>
>> We could probably also limit the set of verbs, e.g. replace "could
>> not" with "failed to" as it's practically the same thing (assuming we
>> pick (a)).
>
> That's true. I would vote for option (a).
I didn't get any comments about Michal's proposal. Can I conclude from
this that (a) above is ok for everyone?
--
Kalle Valo
next prev parent reply other threads:[~2014-03-11 11:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 15:43 [PATCH] ath10k: unify warning messages in mac.c Kalle Valo
2014-03-03 16:23 ` Michal Kazior
2014-03-03 16:40 ` Kalle Valo
2014-03-11 11:16 ` Kalle Valo [this message]
2014-03-11 17:37 ` Ben Greear
2014-03-11 17:46 ` Joe Perches
2014-03-11 17:56 ` Ben Greear
2014-03-11 18:08 ` Joe Perches
-- strict thread matches above, loose matches on Subject: below --
2014-03-24 15:00 Kalle Valo
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=87k3c1gf35.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.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).