From: Johannes Berg <johannes@sipsolutions.net>
To: Henning Rogge <hrogge@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Bob Copeland <me@bobcopeland.com>,
Thomas Pedersen <thomas@noack.us>,
Yeoh Chun-Yeow <yeohchunyeow@gmail.com>
Subject: Re: [RFC Patch] Unify mpp/mesh_path handling for Mac 802.11s
Date: Thu, 22 May 2014 17:25:31 +0200 [thread overview]
Message-ID: <1400772331.4174.38.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CAGnRvur6zFrUUbSLzC=PddHqO46k5RbQM+RY19o_hqZxbQnzHw@mail.gmail.com> (sfid-20140522_172136_696770_B3DD90A6)
On Thu, 2014-05-22 at 17:21 +0200, Henning Rogge wrote:
> Ups...
>
> I thought I had found all this "stupid whitespace mistakes, I will
> remove them in the next version of the patch...
:)
> but I wanted a comment
> if this is a good direction to go before we discuss how to change the
> netlink interface to export the data of the former mpp_paths table.
No idea, really. However, I'm not sure why the two are related? The
netlink API could just iterate two tables as well.
johannes
next prev parent reply other threads:[~2014-05-22 15:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 15:06 [RFC Patch] Unify mpp/mesh_path handling for Mac 802.11s Henning Rogge
2014-05-22 15:15 ` Johannes Berg
2014-05-22 15:21 ` Henning Rogge
2014-05-22 15:25 ` Johannes Berg [this message]
2014-05-22 19:27 ` Bob Copeland
2014-05-22 19:31 ` Henning Rogge
2014-05-23 9:08 ` Yeoh Chun-Yeow
2014-05-23 10:52 ` Henning Rogge
2014-05-23 20:57 ` Bob Copeland
2014-05-26 6:47 ` Yeoh Chun-Yeow
2014-05-26 9:37 ` Henning Rogge
2014-05-26 10:26 ` Yeoh Chun-Yeow
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=1400772331.4174.38.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=hrogge@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=me@bobcopeland.com \
--cc=thomas@noack.us \
--cc=yeohchunyeow@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).