All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rikard Falkeborn <rikard.falkeborn@gmail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
	"David S. Miller" <davem@davemloft.net>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>
Cc: linux-crypto@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	linux-kernel@vger.kernel.org,
	Rikard Falkeborn <rikard.falkeborn@gmail.com>
Subject: [PATCH 0/3] drivers/crypto: Constify static attribute_group
Date: Thu, 10 Feb 2022 21:28:02 +0100	[thread overview]
Message-ID: <20220210202805.7750-1-rikard.falkeborn@gmail.com> (raw)

This series constifies a couple of static attribute_group structs that
are not modified. This allows the compiler to put them in read-only
memory. The patches are independent and can be applied in any order (and
go through different trees if needed).

Rikard Falkeborn (3):
  crypto: omap-aes - Constify static attribute_group
  crypto: omap-sham - Constify static attribute_group
  crypto/nx: Constify static attribute_group structs

 drivers/crypto/nx/nx-common-pseries.c | 4 ++--
 drivers/crypto/omap-aes.c             | 2 +-
 drivers/crypto/omap-sham.c            | 2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)

-- 
2.35.1


WARNING: multiple messages have this Message-ID (diff)
From: Rikard Falkeborn <rikard.falkeborn@gmail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
	"David S. Miller" <davem@davemloft.net>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@lists.ozlabs.org, linux-crypto@vger.kernel.org,
	Rikard Falkeborn <rikard.falkeborn@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] drivers/crypto: Constify static attribute_group
Date: Thu, 10 Feb 2022 21:28:02 +0100	[thread overview]
Message-ID: <20220210202805.7750-1-rikard.falkeborn@gmail.com> (raw)

This series constifies a couple of static attribute_group structs that
are not modified. This allows the compiler to put them in read-only
memory. The patches are independent and can be applied in any order (and
go through different trees if needed).

Rikard Falkeborn (3):
  crypto: omap-aes - Constify static attribute_group
  crypto: omap-sham - Constify static attribute_group
  crypto/nx: Constify static attribute_group structs

 drivers/crypto/nx/nx-common-pseries.c | 4 ++--
 drivers/crypto/omap-aes.c             | 2 +-
 drivers/crypto/omap-sham.c            | 2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)

-- 
2.35.1


             reply	other threads:[~2022-02-10 20:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10 20:28 Rikard Falkeborn [this message]
2022-02-10 20:28 ` [PATCH 0/3] drivers/crypto: Constify static attribute_group Rikard Falkeborn
2022-02-10 20:28 ` [PATCH 1/3] crypto: omap-aes - " Rikard Falkeborn
2022-02-10 20:28   ` Rikard Falkeborn
2022-02-10 20:28 ` [PATCH 2/3] crypto: omap-sham " Rikard Falkeborn
2022-02-10 20:28   ` Rikard Falkeborn
2022-02-10 20:28 ` [PATCH 3/3] crypto/nx: Constify static attribute_group structs Rikard Falkeborn
2022-02-10 20:28   ` Rikard Falkeborn
2022-02-11  6:27   ` Daniel Axtens
2022-02-18  5:37 ` [PATCH 0/3] drivers/crypto: Constify static attribute_group Herbert Xu
2022-02-18  5:37   ` 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=20220210202805.7750-1-rikard.falkeborn@gmail.com \
    --to=rikard.falkeborn@gmail.com \
    --cc=benh@kernel.crashing.org \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=paulus@samba.org \
    /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.