devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: herbert@gondor.apana.org.au
Cc: rsahu@apm.com, vinod.koul@intel.com, dan.j.williams@intel.com,
	dmaengine@vger.kernel.org, arnd@arndb.de,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, jcm@redhat.com,
	patches@apm.com, linux-crypto@vger.kernel.org, kgondkar@apm.com
Subject: Re: [PATCH v2 0/3] dmaengine: Add supports for APM X-Gene SoC CRC32C accerlerator driver
Date: Wed, 09 Dec 2015 12:37:16 -0500 (EST)	[thread overview]
Message-ID: <20151209.123716.1633991691492130781.davem@davemloft.net> (raw)
In-Reply-To: <20151209084458.GA26803@gondor.apana.org.au>

From: Herbert Xu <herbert@gondor.apana.org.au>
Date: Wed, 9 Dec 2015 16:44:58 +0800

> On Wed, Dec 09, 2015 at 02:13:32PM +0530, Rameshwar Sahu wrote:
>>
>> Yes, we are not upstream in-kernel users right now, but later client
>> ma upstream there patches.
> 
> Well I'd prefer to not take any crypto drivers that don't have
> in-kernel users.

+1

  reply	other threads:[~2015-12-09 17:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-16  9:12 [PATCH v2 0/3] dmaengine: Add supports for APM X-Gene SoC CRC32C accerlerator driver rsahu
2015-11-30  8:36 ` Rameshwar Sahu
2015-11-30  8:39   ` Herbert Xu
2015-11-30  8:49     ` Rameshwar Sahu
2015-11-30  8:50       ` Herbert Xu
2015-11-30  8:57         ` Rameshwar Sahu
2015-12-09  8:25 ` Rameshwar Sahu
2015-12-09  8:27   ` Herbert Xu
2015-12-09  8:43     ` Rameshwar Sahu
2015-12-09  8:44       ` Herbert Xu
2015-12-09 17:37         ` David Miller [this message]
     [not found] <rsahu@apm.com>
2015-11-16  9:08 ` rsahu-qTEPVZfXA3Y
  -- strict thread matches above, loose matches on Subject: below --
2015-11-07 16:37 Rameshwar Prasad Sahu

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=20151209.123716.1633991691492130781.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=arnd@arndb.de \
    --cc=dan.j.williams@intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=jcm@redhat.com \
    --cc=kgondkar@apm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@apm.com \
    --cc=rsahu@apm.com \
    --cc=vinod.koul@intel.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 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).