From: Kalle Valo <kalle.valo@iki.fi>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: python nl80211 code
Date: Tue, 01 Dec 2009 13:52:44 +0200 [thread overview]
Message-ID: <87skbu6hdf.fsf@purkki.valot.fi> (raw)
In-Reply-To: <1259668202.32171.73.camel@johannes.local> (Johannes Berg's message of "Tue\, 01 Dec 2009 12\:50\:02 +0100")
Johannes Berg <johannes@sipsolutions.net> writes:
>> Ok, good to know. What do you think if I remove the parsing of
>> nl80211.h and instead add the nl80211 commands manually as python
>> code? Sure, it's monkey code but easier to maintain IMHO.
>
> Yeah, I agree.
Good. I'll do that then.
>> Or have some intermediate language, maybe. Any ideas?
>
> I guess we could use sparse to output introspection information for
> nl80211.h instead, but is it worth it?
Increases coolness factory but that's about it =)
--
Kalle Valo
prev parent reply other threads:[~2009-12-01 11:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 8:53 python nl80211 code Kalle Valo
2009-12-01 9:23 ` Johannes Berg
2009-12-01 10:31 ` Kalle Valo
2009-12-01 11:24 ` Johannes Berg
2009-12-01 11:47 ` Kalle Valo
2009-12-01 11:50 ` Johannes Berg
2009-12-01 11:52 ` Kalle Valo [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=87skbu6hdf.fsf@purkki.valot.fi \
--to=kalle.valo@iki.fi \
--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 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.