From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: andrey.konovalov@linaro.org, emmanuel.grumbach@intel.com,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: fix kernel-doc comments in mac80211.h
Date: Thu, 28 May 2015 14:36:49 +0200 [thread overview]
Message-ID: <1432816609.2459.3.camel@sipsolutions.net> (raw)
In-Reply-To: <1432816470.6319.41.camel@decadent.org.uk>
On Thu, 2015-05-28 at 13:34 +0100, Ben Hutchings wrote:
> It's a build failure so it should go upstream now.
Ok, I was under the impression it's a warning.
I guess I'll just have to send a copy of the commit to 4.1 then - git
will sort out getting it twice I suppose.
johannes
next prev parent reply other threads:[~2015-05-28 12:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 20:39 [PATCH] mac80211: fix kernel-doc comments in mac80211.h andrey.konovalov
2015-05-20 13:03 ` Johannes Berg
2015-05-27 23:30 ` Ben Hutchings
2015-05-28 7:00 ` Johannes Berg
2015-05-28 12:34 ` Ben Hutchings
2015-05-28 12:36 ` Johannes Berg [this message]
2015-06-01 2:51 ` Randy Dunlap
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=1432816609.2459.3.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=andrey.konovalov@linaro.org \
--cc=ben@decadent.org.uk \
--cc=emmanuel.grumbach@intel.com \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).