From: David Miller <davem@davemloft•net>
To: jens.axboe@oracle•com
Cc: torvalds@linux-foundation•org, eric.dumazet@gmail•com,
jgunthorpe@obsidianresearch•com, vl@samba•org,
opurdila@ixiacom•com, netdev@vger•kernel.org,
linux-kernel@vger•kernel.org
Subject: Re: SPLICE_F_NONBLOCK semantics...
Date: Fri, 02 Oct 2009 09:45:24 -0700 (PDT) [thread overview]
Message-ID: <20091002.094524.50318302.davem@davemloft.net> (raw)
In-Reply-To: <20091002074754.GE14918@kernel.dk>
From: Jens Axboe <jens.axboe@oracle•com>
Date: Fri, 2 Oct 2009 09:47:54 +0200
> The net patch looks fine and correct to me, feel free to add my acked-by
> if you want.
Thanks Jens.
prev parent reply other threads:[~2009-10-02 16:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 22:11 SPLICE_F_NONBLOCK semantics David Miller
2009-10-01 22:21 ` Linus Torvalds
2009-10-01 22:24 ` Linus Torvalds
2009-10-01 22:27 ` David Miller
2009-10-02 7:47 ` Jens Axboe
2009-10-02 16:45 ` David Miller [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=20091002.094524.50318302.davem@davemloft.net \
--to=davem@davemloft$(echo .)net \
--cc=eric.dumazet@gmail$(echo .)com \
--cc=jens.axboe@oracle$(echo .)com \
--cc=jgunthorpe@obsidianresearch$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=opurdila@ixiacom$(echo .)com \
--cc=torvalds@linux-foundation$(echo .)org \
--cc=vl@samba$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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