From: Rikard Falkeborn <rikard.falkeborn@gmail.com>
To: Gilad Ben-Yossef <gilad@benyossef.com>,
Zaibo Xu <xuzaibo@huawei.com>,
Zhou Wang <wangzhou1@hisilicon.com>
Cc: herbert@gondor.apana.org.au, davem@davemloft.net,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
Rikard Falkeborn <rikard.falkeborn@gmail.com>
Subject: [PATCH 0/4] crypto: constify struct debugfs_reg32
Date: Sat, 9 May 2020 00:34:58 +0200 [thread overview]
Message-ID: <20200508223502.7258-1-rikard.falkeborn@gmail.com> (raw)
A small series constifying struct debugfs_reg32 where it can be made
const. There's no dependency between the patches.
Rikard Falkeborn (4):
crypto: ccree - constify struct debugfs_reg32
crypto: hisilicon/hpre - constify struct debugfs_reg32
crypto: hisilicon/zip - constify struct debugfs_reg32
crypto: hisilicon/sec2 - constify sec_dfx_regs
drivers/crypto/ccree/cc_debugfs.c | 4 ++--
drivers/crypto/hisilicon/hpre/hpre_main.c | 4 ++--
drivers/crypto/hisilicon/sec2/sec_main.c | 2 +-
drivers/crypto/hisilicon/zip/zip_main.c | 2 +-
4 files changed, 6 insertions(+), 6 deletions(-)
--
2.26.2
next reply other threads:[~2020-05-08 22:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 22:34 Rikard Falkeborn [this message]
2020-05-08 22:34 ` [PATCH 1/4] crypto: ccree - constify struct debugfs_reg32 Rikard Falkeborn
2020-05-08 22:35 ` [PATCH 2/4] crypto: hisilicon/hpre " Rikard Falkeborn
2020-05-08 22:35 ` [PATCH 3/4] crypto: hisilicon/zip " Rikard Falkeborn
2020-05-09 1:49 ` Zhou Wang
2020-05-08 22:35 ` [PATCH 4/4] crypto: hisilicon/sec2 - constify sec_dfx_regs Rikard Falkeborn
2020-05-15 6:21 ` [PATCH 0/4] crypto: constify struct debugfs_reg32 Herbert Xu
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=20200508223502.7258-1-rikard.falkeborn@gmail.com \
--to=rikard.falkeborn@gmail.com \
--cc=davem@davemloft.net \
--cc=gilad@benyossef.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wangzhou1@hisilicon.com \
--cc=xuzaibo@huawei.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.