From: Johannes Berg <johannes@sipsolutions.net>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 0/3] wireless extensions improvements
Date: Fri, 26 Jun 2009 22:12:47 +0200 [thread overview]
Message-ID: <1246047167.21314.61.camel@johannes.local> (raw)
In-Reply-To: <20090625.161817.112930127.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
On Thu, 2009-06-25 at 16:18 -0700, David Miller wrote:
> These changes look fine to me, so I'll likely put them into
> net-next-2.6 as soon as I open that up.
Alright, sounds good.
> FWIW, I bet we could make read() easily work properly to for the
> compat stuff, and it would be nice to shore up that one minor hole.
Yes, but I think that would require introducing compat_sys_read() and
touching all architectures.
One other thing I just thought about -- the things you were mentioning
wrt. u64 alignment, is that relevant for sendmsg() as well? This doesn't
cover that at all, so far, obviously. If that would be needed, we'd also
need more work there, we can of course do that as we go along and add
code to deal with just the kernel->userspace messages where necessary.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
prev parent reply other threads:[~2009-06-29 7:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 11:34 [PATCH 0/3] wireless extensions improvements Johannes Berg
2009-06-24 11:34 ` [PATCH 1/3] wireless extensions: make netns aware Johannes Berg
2009-06-24 11:34 ` [PATCH 2/3] wext: optimise, comment and fix event sending Johannes Berg
2009-06-24 11:34 ` [PATCH 3/3] net/compat/wext: send different messages to compat tasks Johannes Berg
2009-07-01 21:26 ` [PATCH 3/3 v3] " Johannes Berg
2009-07-15 16:08 ` David Miller
2009-06-25 23:18 ` [PATCH 0/3] wireless extensions improvements David Miller
2009-06-26 5:46 ` John W. Linville
2009-06-26 20:12 ` Johannes Berg [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=1246047167.21314.61.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=davem@davemloft.net \
--cc=linux-wireless@vger.kernel.org \
--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).