From: Johannes Berg <johannes@sipsolutions.net>
To: "Rob Herring" <robh+dt@kernel.org>, "Rafał Miłecki" <zajec5@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
"Martin Blumenstingl" <martin.blumenstingl@googlemail.com>,
"Felix Fietkau" <nbd@nbd.name>,
"Arend van Spriel" <arend@broadcom.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: [PATCH V6 1/3] dt-bindings: document common IEEE 802.11 frequency limit property
Date: Thu, 05 Jan 2017 12:51:29 +0100 [thread overview]
Message-ID: <1483617089.4394.13.camel@sipsolutions.net> (raw)
In-Reply-To: <CAL_JsqLg5YkC-YUHg6mQ35nmGaG7SC33VJB++fgtZsu1fRV-7Q@mail.gmail.com>
> Acked-by: Rob Herring <robh@kernel.org>
Do I take that to mean that we'll merge it through the subsystem tree,
and not go through some common DT tree?
Thanks,
johannes
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: "Rob Herring" <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
"Rafał Miłecki" <zajec5-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-wireless
<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"Martin Blumenstingl"
<martin.blumenstingl-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>,
"Felix Fietkau" <nbd-Vt+b4OUoWG0@public.gmane.org>,
"Arend van Spriel"
<arend-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>,
"Arnd Bergmann" <arnd-r2nGTMty4D4@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"Rafał Miłecki" <rafal-g1n6cQUeyibVItvQsEIGlw@public.gmane.org>
Subject: Re: [PATCH V6 1/3] dt-bindings: document common IEEE 802.11 frequency limit property
Date: Thu, 05 Jan 2017 12:51:29 +0100 [thread overview]
Message-ID: <1483617089.4394.13.camel@sipsolutions.net> (raw)
In-Reply-To: <CAL_JsqLg5YkC-YUHg6mQ35nmGaG7SC33VJB++fgtZsu1fRV-7Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
> Acked-by: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Do I take that to mean that we'll merge it through the subsystem tree,
and not go through some common DT tree?
Thanks,
johannes
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-01-05 11:52 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 17:58 [PATCH V6 1/3] dt-bindings: document common IEEE 802.11 frequency limit property Rafał Miłecki
2017-01-04 17:58 ` Rafał Miłecki
2017-01-04 17:58 ` [PATCH V6 2/3] cfg80211: move function checking range fit to util.c Rafał Miłecki
2017-01-04 17:58 ` Rafał Miłecki
2017-01-04 17:58 ` [PATCH V6 3/3] cfg80211: support ieee80211-freq-limit DT property Rafał Miłecki
2017-01-04 17:58 ` Rafał Miłecki
2017-01-04 17:58 ` [PATCH V6 4/3] brcmfmac: use wiphy_read_of_freq_limits to respect extra limits Rafał Miłecki
2017-01-04 17:58 ` Rafał Miłecki
2017-01-04 20:07 ` Arend Van Spriel
2017-01-04 20:07 ` Arend Van Spriel
2017-01-04 21:19 ` Rafał Miłecki
2017-01-04 21:19 ` Rafał Miłecki
2017-01-05 9:31 ` Arend Van Spriel
2017-01-05 9:31 ` Arend Van Spriel
2017-01-05 10:02 ` Rafał Miłecki
2017-01-05 10:02 ` Rafał Miłecki
2017-01-07 12:52 ` Arend Van Spriel
2017-01-07 12:52 ` Arend Van Spriel
2017-01-07 12:58 ` Rafał Miłecki
2017-01-07 12:58 ` Rafał Miłecki
2017-01-09 8:58 ` Johannes Berg
2017-01-09 8:58 ` Johannes Berg
2017-01-09 11:02 ` Arend Van Spriel
2017-01-09 11:02 ` Arend Van Spriel
2017-01-09 11:07 ` Johannes Berg
2017-01-09 11:07 ` Johannes Berg
2017-01-07 17:36 ` Rafał Miłecki
2017-01-07 17:36 ` Rafał Miłecki
2017-01-04 19:46 ` [PATCH V6 1/3] dt-bindings: document common IEEE 802.11 frequency limit property Rob Herring
2017-01-04 19:46 ` Rob Herring
2017-01-05 11:51 ` Johannes Berg [this message]
2017-01-05 11:51 ` Johannes Berg
2017-01-05 16:34 ` Rob Herring
2017-01-05 16:34 ` Rob Herring
2017-01-06 12:59 ` Johannes Berg
2017-01-06 12:59 ` Johannes Berg
2017-01-07 12:53 ` Rafał Miłecki
2017-01-07 12:53 ` Rafał Miłecki
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=1483617089.4394.13.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend@broadcom.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=nbd@nbd.name \
--cc=rafal@milecki.pl \
--cc=robh+dt@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.