All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ying Xue <ying.xue@windriver.com>
To: David Miller <davem@davemloft.net>
Cc: <viro@ZenIV.linux.org.uk>, <hch@lst.de>, <netdev@vger.kernel.org>,
	<erik.hugne@ericsson.com>, <jon.maloy@ericsson.com>
Subject: Re: [PATCH net-next 0/2] net: Remove iocb argument from sendmsg and recvmsg
Date: Mon, 2 Mar 2015 08:52:56 +0800	[thread overview]
Message-ID: <54F3B468.1060204@windriver.com> (raw)
In-Reply-To: <20150228.171250.1612351664541183290.davem@davemloft.net>

On 03/01/2015 06:12 AM, David Miller wrote:
> From: Ying Xue <ying.xue@windriver.com>
> Date: Fri, 27 Feb 2015 19:06:35 +0800
> 
>> Currently there is only one user - TIPC whose sendmsg() instances
>> using iocb argument. Meanwhile, there is no user using iocb argument
>> in its recvmsg() instance. Therefore, if we eliminate the werid usage
>> of iobc argument from TIPC, the iocb argument can be removed from
>> all sendmsg() and recvmsg() instances of the whole network stack.
>>
>> By the way, as patch #2 is very big, I can divide it into smaller
>> patches regarding module in next version if necessary.
>>
>> Reference:
>> https://patchwork.ozlabs.org/patch/433960/
> 
> You didn't even properly compile test this patch series:
> 
> net/dccp/proto.c:744:5: error: conflicting types for ‘dccp_sendmsg’
>  int dccp_sendmsg(struct sock *sk, struct msghdr *msg, size_t len)
>      ^
> In file included from net/dccp/proto.c:37:0:
> net/dccp/dccp.h:313:5: note: previous declaration of ‘dccp_sendmsg’ was here
>  int dccp_sendmsg(struct kiocb *iocb, struct sock *sk, struct msghdr *msg,
>      ^
>  ...
> net/dccp/proto.c:808:5: error: conflicting types for ‘dccp_recvmsg’
>  int dccp_recvmsg(struct sock *sk, struct msghdr *msg, size_t len, int nonblock,
>      ^
> In file included from net/dccp/proto.c:37:0:
> net/dccp/dccp.h:315:5: note: previous declaration of ‘dccp_recvmsg’ was here
>  int dccp_recvmsg(struct kiocb *iocb, struct sock *sk,
>      ^
> 

Oops! When I verified it, I almost enabled all functions and modules associated
with networking except DCCP module I accidentally missed. Thank you for the
report. I would carefully verified the patch again.

Regards,
Ying

      reply	other threads:[~2015-03-02  0:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-27 11:06 [PATCH net-next 0/2] net: Remove iocb argument from sendmsg and recvmsg Ying Xue
2015-02-27 11:06 ` [PATCH net-next 1/2] tipc: Don't use iocb argument in socket layer Ying Xue
2015-02-27 13:30   ` Jon Maloy
2015-02-28  2:29     ` Ying Xue
2015-02-28 21:59     ` David Miller
2015-02-27 11:06 ` [PATCH net-next 2/2] net: Remove iocb argument from sendmsg and recvmsg Ying Xue
2015-02-28 22:12 ` [PATCH net-next 0/2] " David Miller
2015-03-02  0:52   ` Ying Xue [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=54F3B468.1060204@windriver.com \
    --to=ying.xue@windriver.com \
    --cc=davem@davemloft.net \
    --cc=erik.hugne@ericsson.com \
    --cc=hch@lst.de \
    --cc=jon.maloy@ericsson.com \
    --cc=netdev@vger.kernel.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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.