From: Herbert Xu <herbert@gondor.apana.org.au>
To: David Miller <davem@davemloft.net>
Cc: ayush.sawal@chelsio.com, netdev@vger.kernel.org,
secdev@chelsio.com, lkp@intel.com,
Steffen Klassert <steffen.klassert@secunet.com>
Subject: Re: [PATCH net V2] Crypto/chcr: Registering cxgb4 to xfrmdev_ops
Date: Sat, 25 Jul 2020 16:20:34 +1000 [thread overview]
Message-ID: <20200725062034.GA19493@gondor.apana.org.au> (raw)
In-Reply-To: <20200724.170108.362782113011946610.davem@davemloft.net>
On Fri, Jul 24, 2020 at 05:01:08PM -0700, David Miller wrote:
>
> Please start submitting chcr patches to the crypto subsystem, where it
> belongs, instead of the networking GIT trees.
Hi Dave:
I think this patch belongs to the networking tree. The reason is
that it's related to xfrm offload which has nothing to do with the
Crypto API.
Do xfrm offload drivers usually go through the networking tree or
would it be better directed through the xfrm tree?
There's really nobody on the crypto mailing list who could give
this the proper review that it deserves.
Of course I'm happy to continue taking anything that touches
chcr_algo.c as that resides wholly within the Crypto API.
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
next prev parent reply other threads:[~2020-07-25 6:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 8:41 [PATCH net V2] Crypto/chcr: Registering cxgb4 to xfrmdev_ops Ayush Sawal
2020-07-25 0:01 ` David Miller
2020-07-25 6:20 ` Herbert Xu [this message]
2020-07-27 9:16 ` Steffen Klassert
2020-07-27 9:59 ` Ayush Sawal
2020-07-28 13:01 ` Vinay Kumar Yadav
2020-07-29 0:18 ` 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=20200725062034.GA19493@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=ayush.sawal@chelsio.com \
--cc=davem@davemloft.net \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=secdev@chelsio.com \
--cc=steffen.klassert@secunet.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.