From: Kalle Valo <kvalo@codeaurora.org>
To: Helmut Schaa <helmut.schaa@googlemail.com>
Cc: Paul McQuade <paulmcquad@gmail.com>,
Stanislaw Gruszka <sgruszka@redhat.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] net: wireless: rt2x00: Fixed Spacing issues
Date: Thu, 21 Jan 2016 19:12:34 +0200 [thread overview]
Message-ID: <87oaceyhz1.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAGXE3d-3M6s0k0rbA2-vihLfwvjhdVgxDsQSt_84WxXme+U7bg@mail.gmail.com> (Helmut Schaa's message of "Thu, 21 Jan 2016 18:02:45 +0100")
Helmut Schaa <helmut.schaa@googlemail.com> writes:
> On Thu, Jan 21, 2016 at 5:56 PM, Helmut Schaa
> <helmut.schaa@googlemail.com> wrote:
>> On Sat, Oct 17, 2015 at 10:04 PM, Paul McQuade <paulmcquad@gmail.com> wrote:
>>> Removed empty spaces before/after parenthesis
>>>
>>> Signed-off-by: Paul McQuade <paulmcquad@gmail.com>
>>
>> Just noticed these did not get applied by Kalle yet.
>
> Kalle, can you fix up the path (ralink/rt2x00 instead of rt2x00) when applying?
> Or would you prefer Paul to respin the whole code style cleanup series?
Actually git should be manage that automatically, it's so awesome :)
I can also fix the title and remove the unnecessary "net: wireless:"
prefix.
--
Kalle Valo
next prev parent reply other threads:[~2016-01-21 17:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-17 20:04 [PATCH] net: wireless: rt2x00: Fixed Spacing issues Paul McQuade
2016-01-21 16:56 ` Helmut Schaa
2016-01-21 17:02 ` Helmut Schaa
2016-01-21 17:12 ` Kalle Valo [this message]
2016-02-02 15:59 ` Sudip Mukherjee
2016-02-07 7:10 ` 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=87oaceyhz1.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=helmut.schaa@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paulmcquad@gmail.com \
--cc=sgruszka@redhat.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).