From: Johannes Berg <johannes@sipsolutions.net>
To: "Rafał Miłecki" <zajec5@gmail.com>, linux-wireless@vger.kernel.org
Cc: linux-doc@vger.kernel.org, "Rafał Miłecki" <rafal@milecki.pl>,
"Seth Forshee" <seth.forshee@canonical.com>
Subject: Re: [PATCH 1/2] cfg80211: update wireless-regdb repo url in Documentation
Date: Mon, 02 Jan 2017 12:01:17 +0100 [thread overview]
Message-ID: <1483354877.4596.10.camel@sipsolutions.net> (raw)
In-Reply-To: <20170102072829.9766-1-zajec5@gmail.com> (sfid-20170102_082841_713230_EB380D37)
On Mon, 2017-01-02 at 08:28 +0100, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> It's maintained by Seth Forshe for a long time now.
>
Both applied, thanks.
johannes
prev parent reply other threads:[~2017-01-02 11:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-02 7:28 [PATCH 1/2] cfg80211: update wireless-regdb repo url in Documentation Rafał Miłecki
2017-01-02 7:28 ` [PATCH 2/2] cfg80211: fix example REG_RULE usage " Rafał Miłecki
2017-01-02 11:01 ` Johannes Berg [this message]
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=1483354877.4596.10.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rafal@milecki.pl \
--cc=seth.forshee@canonical.com \
--cc=zajec5@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).