From: Herbert Xu <herbert@gondor.apana.org.au>
To: Tadeusz Struk <tadeusz.struk@intel.com>
Cc: David Miller <davem@davemloft.net>,
linux-aio@kvack.org, netdev@vger.kernel.org,
ying.xue@windriver.com, bcrl@kvack.org, viro@ZenIV.linux.org.uk,
linux-fsdevel@vger.kernel.org, hch@lst.de,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH v3 net-next 0/3] Add support for async socket operations
Date: Tue, 24 Mar 2015 22:29:52 +1100 [thread overview]
Message-ID: <20150324112952.GC11405@gondor.apana.org.au> (raw)
In-Reply-To: <551081F1.9090303@intel.com>
On Mon, Mar 23, 2015 at 02:13:21PM -0700, Tadeusz Struk wrote:
>
> Herbert, is it possible to pull it to cryptodev?
How many more changes do you have that sit on top of this? If
it's small we could just push them through net-next until the
merge window opens again.
Cheers,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To unsubscribe, send a message with 'unsubscribe linux-aio' in
the body to majordomo@kvack.org. For more info on Linux AIO,
see: http://www.kvack.org/aio/
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>
prev parent reply other threads:[~2015-03-24 11:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 19:31 [PATCH v3 net-next 0/3] Add support for async socket operations Tadeusz Struk
2015-03-19 19:31 ` [PATCH v3 net-next 1/3] net: socket: add support for async operations Tadeusz Struk
2015-03-19 19:31 ` [PATCH v3 net-next 2/3] crypto: af_alg - Allow to link sgl Tadeusz Struk
2015-03-19 19:31 ` [PATCH v3 net-next 3/3] crypto: algif - change algif_skcipher to be asynchronous Tadeusz Struk
2015-03-19 19:51 ` [PATCH v3 net-next 0/3] Add support for async socket operations Al Viro
2015-03-20 6:45 ` Christoph Hellwig
2015-03-23 20:42 ` David Miller
2015-03-23 21:13 ` Tadeusz Struk
2015-03-24 11:29 ` Herbert Xu [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=20150324112952.GC11405@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=bcrl@kvack.org \
--cc=davem@davemloft.net \
--cc=hch@lst.de \
--cc=linux-aio@kvack.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tadeusz.struk@intel.com \
--cc=viro@ZenIV.linux.org.uk \
--cc=ying.xue@windriver.com \
/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.