From: Florian Sesser <flomaillist@cosetrain.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, Benedikt Elser <elser@in.tum.de>
Subject: Re: [PATCH 3/3] mac80211: Modul. mesh path prot: Skeleton Module
Date: Mon, 09 Feb 2009 12:58:16 +0100 [thread overview]
Message-ID: <49901A58.4030403@cosetrain.com> (raw)
In-Reply-To: <1234176251.4175.222.camel@johannes.local>
Hi!
Johannes, thanks for all of your comments! I will need some time to work
through them, though, please be patient.
Johannes Berg wrote:
> 00-0F-0F (hex) Real ID Technology Co., Ltd.
> 000F0F (base 16) Real ID Technology Co., Ltd.
> 9F Hanmi B/D 192-19
> Nonhyeon-Dong
> Gangnam-Gu Seoul 135-010
> KOREA, REPUBLIC OF
>
> Have you asked them about using their OUI?
Nah, sorry about that - I didn't get 0x000FACFF meant 'null' in the
first place, and since I don't have access to an OUI yet, I selected
this value by random. I still hope nobody seriously wants my skeleton
module in the kernel code though.
BTW... do you know which OUI in that case (at devel time, this is an
university project, afaik the university does not have an OUI I can use)
makes sense for stuff like that? I believe there is a reserved range,
but I don't know for what reason it's reserved, and if I should use it
to avoid misunderstandings.
>> +config MAC80211_MESH_PP_TEST
>> + tristate "80211s: Path selection protocol test module"
>> + default n
>> + depends on MAC80211_MESH && MAC80211 && EXPERIMENTAL && m
>
> && m ???
Limits the tristate to 'n' or 'm', because I didn't want to clutter the
code with ifdefs for the 'compiled-in' case. This cannot be the final
solution either. I need to investigate some more on what happens if I
just compile it in.
[do you really think I should to copy the style of rate control? i don't
like it at all. they have KBs of (IMHO) not very useful code instead of
keeping it to the point? Even in the Kconfig. Please correct me if I got
this wrong.]
> Generally, this looks like a decent idea,
Thanks :)
> but the execution definitely is lacking.
I know that, as I'm pretty new to kernel coding. Should I get me some
mentor from the kernel mentors project, or are you willing to correct my
stupid beginner mistakes all the time?
Also: As you still haven't said anything about my ops struct, I deem you
think I have made a somewhat reasonable selection here?
Again, thanks a lot!
Florian
next prev parent reply other threads:[~2009-02-09 11:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-08 19:47 [RFC/RFT v2] mac80211 / o11s mesh: Modularize Path Selection Protocol Florian Sesser
2009-02-08 19:52 ` [PATCH 1/3] mac80211: Modularize Mesh path selection protocol Florian Sesser
2009-02-08 19:52 ` [PATCH 2/3] mac80211: Modul. mesh path prot: Comm w/ Userspace Florian Sesser
2009-02-09 10:39 ` Johannes Berg
2009-02-08 19:52 ` [PATCH 3/3] mac80211: Modul. mesh path prot: Skeleton Module Florian Sesser
2009-02-09 10:44 ` Johannes Berg
2009-02-09 11:58 ` Florian Sesser [this message]
2009-02-09 12:14 ` Johannes Berg
2009-02-09 10:35 ` [PATCH 1/3] mac80211: Modularize Mesh path selection protocol Johannes Berg
2009-02-08 19:56 ` [PATCH 1/1] iw: Added capability to set individual mesh IDs Florian Sesser
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=49901A58.4030403@cosetrain.com \
--to=flomaillist@cosetrain.com \
--cc=elser@in.tum.de \
--cc=johannes@sipsolutions.net \
--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).