From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Fabian Frederick <fabf@skynet.be>,
linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 1/1 net-next] net: rfkill: kernel-doc warning fixes
Date: Thu, 9 Oct 2014 11:33:59 -0400 [thread overview]
Message-ID: <20141009153359.GA13986@tuxdriver.com> (raw)
In-Reply-To: <1412846213.1828.28.camel@jlt4.sipsolutions.net>
On Thu, Oct 09, 2014 at 11:16:53AM +0200, Johannes Berg wrote:
> Applied, with a somewhat better changelog.
FWIW, I had already merged that one as-is -- sorry!
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2014-10-09 15:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 20:20 [PATCH 1/1 net-next] net: rfkill: kernel-doc warning fixes Fabian Frederick
2014-10-09 9:16 ` Johannes Berg
2014-10-09 15:33 ` John W. Linville [this message]
2014-10-09 18:34 ` Johannes Berg
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=20141009153359.GA13986@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=davem@davemloft.net \
--cc=fabf@skynet.be \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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).