From: David Miller <davem@davemloft.net>
To: fw@strlen.de
Cc: netdev@vger.kernel.org, johannes@sipsolutions.net
Subject: Re: [PATCH 5/5] net: sock_aio_write: set CMSG_MSG_COMPAT flag if is_compat_task
Date: Fri, 26 Feb 2010 02:06:33 -0800 (PST) [thread overview]
Message-ID: <20100226.020633.240678771.davem@davemloft.net> (raw)
In-Reply-To: <20100226100305.GA16504@Chamillionaire.breakpoint.cc>
From: Florian Westphal <fw@strlen.de>
Date: Fri, 26 Feb 2010 11:03:05 +0100
> If its necessary to set MSG_CMSG_COMPAT properly for plain
> write() as well to have the patch set merged then
> I'll see about adding such a ->compat_write and will resubmit
> the entire set again once net-next opens again for 2.6.35.
If you can get the VFS folks to take the addition of the
->compat_write hook quickly, I can still merge your patch series for
2.6.34
next prev parent reply other threads:[~2010-02-26 10:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-19 12:41 [PATCH v2 0/5] xfrm: add x86 CONFIG_COMPAT support Florian Westphal
2010-02-19 12:41 ` [PATCH 1/5] netlink: append NLMSG_DONE to compatskb, too Florian Westphal
2010-02-19 12:41 ` [PATCH 2/5] netlink: store MSG_CMSG_COMPAT flag in netlink_skb_parms Florian Westphal
2010-02-19 12:49 ` Johannes Berg
2010-02-19 13:34 ` Florian Westphal
2010-02-19 12:41 ` [PATCH 3/5] xfrm: split nlmsg allocation and data copying Florian Westphal
2010-02-19 12:41 ` [PATCH 4/5] xfrm: CONFIG_COMPAT support for x86 architecture Florian Westphal
2010-02-19 12:41 ` [PATCH 5/5] net: sock_aio_write: set CMSG_MSG_COMPAT flag if is_compat_task Florian Westphal
2010-02-26 9:16 ` David Miller
2010-02-26 9:17 ` David Miller
2010-02-26 10:03 ` Florian Westphal
2010-02-26 10:06 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-02-15 16:46 xfrm: add x86 CONFIG_COMPAT support Florian Westphal
2010-02-15 16:46 ` [PATCH 5/5] net: sock_aio_write: set CMSG_MSG_COMPAT flag if is_compat_task Florian Westphal
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=20100226.020633.240678771.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=johannes@sipsolutions.net \
--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).