From: Johannes Berg <johannes@sipsolutions.net>
To: Ola Olsson <ola1olsson@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] iw: Fix return values when parameters are wrong
Date: Thu, 08 Oct 2015 09:50:12 +0200 [thread overview]
Message-ID: <1444290612.2131.1.camel@sipsolutions.net> (raw)
In-Reply-To: <CABAco3A+7-gJ6CZ+8qCnt_vnYA35dyzhjwoA4D+6D4iqi8-U=Q@mail.gmail.com> (sfid-20151007_184503_016326_2C91510D)
On Wed, 2015-10-07 at 18:45 +0200, Ola Olsson wrote:
> According to header file, wrong parameters
> yield 1 as return value.
> Also tried to fix the comments since one part
> of it was unreadable.
>
That seems reasonable, but your patch (this one at least) is completely
whitespace damaged. Did you submit it through gmail's web interface?
There's some help on how to use mailers here:
https://kernel.org/doc/Documentation/email-clients.txt
johannes
next prev parent reply other threads:[~2015-10-08 7:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 16:45 [PATCH] iw: Fix return values when parameters are wrong Ola Olsson
2015-10-08 7:50 ` Johannes Berg [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-10-12 7:34 Ola Olsson
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=1444290612.2131.1.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=ola1olsson@gmail.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).