From: Arnd Bergmann <arnd@arndb.de>
To: jt@hpl.hp.com
Cc: netdev@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
linux-kernel@vger.kernel.org
Subject: Re: 32bit compat for rtnetlink wireless extensions?
Date: Mon, 27 Mar 2006 23:10:44 +0200 [thread overview]
Message-ID: <200603272310.44692.arnd@arndb.de> (raw)
In-Reply-To: <20060327184242.GC31478@bougret.hpl.hp.com>
Am Monday 27 March 2006 20:42 schrieb Jean Tourrilhes:
> Actually, when things are passed over RtNetlink, the pointer
> is removed, and the content of IW_HEADER_TYPE_POINT is moved to not
> leave a gap.
Ah, that makes sense, thanks for the explanation.
So if the wireless ioctl interface ever got retired, that code could
get simplified a lot to just pass around a flat data structure, right?
Arnd <><
next prev parent reply other threads:[~2006-03-27 21:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200603261408.48766.arnd@arndb.de>
2006-03-27 18:42 ` 32bit compat for rtnetlink wireless extensions? Jean Tourrilhes
2006-03-27 21:10 ` Arnd Bergmann [this message]
2006-03-27 21:17 ` Jean Tourrilhes
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=200603272310.44692.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@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).