From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Julian Calaby <julian.calaby@gmail.com>
Cc: "Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 2/2] qca-swiss-army-knife: add ath10k trace-cmd plugin
Date: Thu, 5 Sep 2013 08:08:14 +0300 [thread overview]
Message-ID: <87ob87rh35.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAGRGNgXhk6RDMKxtz-9JUW2K76rtwH-W8-gvoTxr0616G-e2rQ@mail.gmail.com> (Julian Calaby's message of "Thu, 5 Sep 2013 14:57:35 +1000")
Hi Julian,
Julian Calaby <julian.calaby@gmail.com> writes:
> On Thu, Sep 5, 2013 at 2:49 PM, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
>> "Luis R. Rodriguez" <rodrigue@qca.qualcomm.com> writes:
>>
>>> On Mon, Aug 19, 2013 at 12:11 PM, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
>>>> This one's a skeleton as well.
>>>>
>>>> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
>>>
>>> Applied both and pushed, thanks!
>>
>> Thanks.
>>
>>> I just removed 3 trailing spaces on the 2 patches. One had two
>>> trailing spaces, the last patch had one.
>>
>> Oh, sorry about that. Any ideas how I could check for those myself?
>
> If you have coloured diff output enabled in git (color.diff = true)
> then they and other whitespace errors are highlighted in red whenever
> you do diffs.
I don't normally have colors enabled (don't like them), but it seems to
be easy to enable with 'git diff --color'. It's just that it doesn't
seem to work in my terminal, I only see the ANSI codes and no colors.
But this is the best way to do that, just need to fix my terminal.
Thanks!
--
Kalle Valo
prev parent reply other threads:[~2013-09-05 5:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 19:11 [PATCH 1/2] qca-swiss-army-knife: add ath6kl trace-cmd plugin Kalle Valo
2013-08-19 19:11 ` [PATCH 2/2] qca-swiss-army-knife: add ath10k " Kalle Valo
2013-09-04 18:57 ` Luis R. Rodriguez
2013-09-05 4:49 ` Kalle Valo
2013-09-05 4:57 ` Joe Perches
2013-09-05 5:03 ` Kalle Valo
2013-09-05 5:38 ` Joe Perches
2013-09-05 4:57 ` Julian Calaby
2013-09-05 5:08 ` Kalle Valo [this message]
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=87ob87rh35.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=julian.calaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rodrigue@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 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.