Netdev List
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: unlisted-recipients:; (no To-header on input)
Cc: dhowells@redhat.com, netdev@vger.kernel.org,
	linux-afs@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] rxrpc: Tx length parameter
Date: Wed, 07 Jun 2017 22:11:03 +0100	[thread overview]
Message-ID: <21315.1496869863@warthog.procyon.org.uk> (raw)
In-Reply-To: <149685280179.8474.3836343127280242150.stgit@warthog.procyon.org.uk>

David Howells <dhowells@redhat.com> wrote:

>  (3) Introduce the RXRPC_TX_LENGTH cmsg.  This can be provided on the first
>      sendmsg() that contributes data to a client call request or a service
>      call reply.  If provided, the user must provide exactly that amount of
>      data or an error will be incurred.

I forgot to change struct rxrpc_send_params::tx_total_len from u64 to s64.
Will repost.

David

  parent reply	other threads:[~2017-06-07 21:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-07 16:26 [PATCH net-next 0/3] rxrpc: Tx length parameter David Howells
2017-06-07 16:26 ` [PATCH net-next 1/3] rxrpc: Provide a getsockopt call to query what cmsgs types are supported David Howells
2017-06-07 16:26 ` [PATCH net-next 2/3] rxrpc: Consolidate sendmsg parameters David Howells
2017-06-07 16:27 ` [PATCH net-next 3/3] rxrpc: Provide a cmsg to specify the amount of Tx data for a call David Howells
2017-06-07 21:11 ` David Howells [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-06-07 21:12 [PATCH net-next 0/3] rxrpc: Tx length parameter David Howells
2017-06-08 15:42 ` David Miller

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=21315.1496869863@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=linux-afs@lists.infradead.org \
    --cc=linux-kernel@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