From: Johannes Berg <johannes@sipsolutions.net>
To: Rostislav Lisovy <lisovy@gmail.com>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
fengguang.wu@intel.com,
Rostislav Lisovy <rostislav.lisovy@fel.cvut.cz>
Subject: Re: [PATCH] cfg80211: Move join/leave_ocb comments to be in the correct order
Date: Tue, 04 Nov 2014 13:55:16 +0100 [thread overview]
Message-ID: <1415105716.2064.17.camel@sipsolutions.net> (raw)
In-Reply-To: <1415105352-4295-1-git-send-email-rostislav.lisovy@fel.cvut.cz> (sfid-20141104_134918_159065_C641379A)
On Tue, 2014-11-04 at 13:49 +0100, Rostislav Lisovy wrote:
> Use the same ordering in the comments section as it
> is in the structure below.
Well, I think I confused you :-)
The report from Fengguang's build bot was actually when there was no
documentation, and then I added it and I guess you thought that it was
sending out the report because it was in the wrong place?
Anyway, I think I'll just leave it as is, and not apply this, ok?
johannes
next prev parent reply other threads:[~2014-11-04 12:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 12:49 [PATCH] cfg80211: Move join/leave_ocb comments to be in the correct order Rostislav Lisovy
2014-11-04 12:55 ` Johannes Berg [this message]
2014-11-04 13:00 ` Rostislav Lisovy
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=1415105716.2064.17.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lisovy@gmail.com \
--cc=rostislav.lisovy@fel.cvut.cz \
/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