From: Joe Perches <joe@perches.com>
To: Jannik Becher <becher.jannik@gmail.com>, gregkh@linuxfoundation.org
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers: wlan-ng: fixed a coding style issue
Date: Thu, 22 Sep 2016 15:05:02 -0700 [thread overview]
Message-ID: <1474581902.8253.37.camel@perches.com> (raw)
In-Reply-To: <20160922215646.19168-1-Becher.Jannik@gmail.com>
On Thu, 2016-09-22 at 23:56 +0200, Jannik Becher wrote:
> removed a space after a cast to obtain the coding style.
Better would be to change the subject to something like:
[PATCH] staging: wlan-ng: Remove unnecessary spaces before casts
next prev parent reply other threads:[~2016-09-22 22:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 21:56 [PATCH] drivers: wlan-ng: fixed a coding style issue Jannik Becher
2016-09-22 22:05 ` Joe Perches [this message]
2016-09-22 22:39 ` becher.jannik
2016-09-22 22:52 ` Joe Perches
-- strict thread matches above, loose matches on Subject: below --
2016-09-22 19:11 Jannik Becher
2016-09-22 20:32 ` Andrey Utkin
2016-09-22 20:52 ` becher.jannik
2016-09-22 21:03 ` Joe Perches
2016-09-22 21:14 ` Andrey Utkin
2016-09-22 18:01 Jannik Becher
2016-09-22 18:27 ` Joe Perches
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=1474581902.8253.37.camel@perches.com \
--to=joe@perches.com \
--cc=becher.jannik@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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