From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Haren Myneni <haren@linux.ibm.com>
Cc: mikey@neuling.org, herbert@gondor.apana.org.au,
npiggin@gmail.com, linux-crypto@vger.kernel.org,
sukadev@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org,
dja@axtens.net
Subject: Re: [PATCH v6 1/9] powerpc/vas: Initialize window attributes for GZIP coprocessor type
Date: Wed, 22 Apr 2020 00:09:44 +1000 (AEST) [thread overview]
Message-ID: <49656d3Gtdz9sSt@ozlabs.org> (raw)
In-Reply-To: <1587114029.2275.1103.camel@hbabu-laptop>
On Fri, 2020-04-17 at 09:00:29 UTC, Haren Myneni wrote:
>
> Initialize send and receive window attributes for GZIP high and
> normal priority types.
>
> Signed-off-by: Haren Myneni <haren@linux.ibm.com>
Series applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/a8c0c69b5e95e8f155480d5203a7bafb8024fd93
cheers
next prev parent reply other threads:[~2020-04-21 14:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 8:55 [PATCH v6 0/9] crypto/nx: Enable GZIP engine and provide userpace API Haren Myneni
2020-04-17 9:00 ` [PATCH v6 1/9] powerpc/vas: Initialize window attributes for GZIP coprocessor type Haren Myneni
2020-04-21 14:09 ` Michael Ellerman [this message]
2020-04-17 9:01 ` [PATCH v6 2/9] powerpc/vas: Define VAS_TX_WIN_OPEN ioctl API Haren Myneni
2020-04-17 9:02 ` [PATCH v6 3/9] powerpc/vas: Add VAS user space API Haren Myneni
2020-04-17 9:02 ` [PATCH v6 4/9] crypto/nx: Initialize coproc entry with kzalloc Haren Myneni
2020-04-17 9:03 ` [PATCH v6 5/9] crypto/nx: Rename nx-842-powernv file name to nx-common-powernv Haren Myneni
2020-04-17 9:09 ` [PATCH v6 6/9] crypto/nx: Make enable code generic to add new GZIP compression type Haren Myneni
2020-04-17 9:10 ` [PATCH v6 7/9] crypto/nx: Enable and setup " Haren Myneni
2020-04-17 9:11 ` [PATCH v6 8/9] crypto/nx: Remove 'pid' in vas_tx_win_attr struct Haren Myneni
2020-04-17 9:11 ` [PATCH v6 9/9] Documentation/powerpc: VAS API Haren Myneni
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=49656d3Gtdz9sSt@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=dja@axtens.net \
--cc=haren@linux.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=npiggin@gmail.com \
--cc=sukadev@linux.vnet.ibm.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).