linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: linux-crypto@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
	"Jason A . Donenfeld " <Jason@zx2c4.com>,
	Ard Biesheuvel <ardb@kernel.org>,
	linux-arm-kernel@lists.infradead.org, linux-mips@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org, linux-riscv@lists.infradead.org,
	linux-s390@vger.kernel.org, sparclinux@vger.kernel.org,
	x86@kernel.org
Subject: [PATCH v2 9/9] MAINTAINERS: drop arch/*/lib/crypto/ pattern
Date: Thu, 19 Jun 2025 12:19:08 -0700	[thread overview]
Message-ID: <20250619191908.134235-10-ebiggers@kernel.org> (raw)
In-Reply-To: <20250619191908.134235-1-ebiggers@kernel.org>

From: Eric Biggers <ebiggers@google.com>

Since all files arch/*/lib/crypto/* have been moved into lib/crypto/,
remove the arch/*/lib/crypto/ file pattern from MAINTAINERS.

Signed-off-by: Eric Biggers <ebiggers@google.com>
---
 MAINTAINERS | 1 -
 1 file changed, 1 deletion(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index a92290fffa163..8ca374b24a806 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -6408,11 +6408,10 @@ M:	Jason A. Donenfeld <Jason@zx2c4.com>
 M:	Ard Biesheuvel <ardb@kernel.org>
 L:	linux-crypto@vger.kernel.org
 S:	Maintained
 T:	git https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git libcrypto-next
 T:	git https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git libcrypto-fixes
-F:	arch/*/lib/crypto/
 F:	lib/crypto/
 
 CRYPTO SPEED TEST COMPARE
 M:	Wang Jinchao <wangjinchao@xfusion.com>
 L:	linux-crypto@vger.kernel.org
-- 
2.50.0



  parent reply	other threads:[~2025-06-19 19:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-19 19:18 [PATCH v2 0/9] lib/crypto: move arch/$(ARCH)/lib/crypto/ to lib/crypto/$(ARCH)/ Eric Biggers
2025-06-19 19:19 ` [PATCH v2 1/9] lib/crypto: arm: move arch/arm/lib/crypto/ into lib/crypto/ Eric Biggers
2025-06-19 19:19 ` [PATCH v2 2/9] lib/crypto: arm64: move arch/arm64/lib/crypto/ " Eric Biggers
2025-06-19 19:19 ` [PATCH v2 3/9] lib/crypto: mips: move arch/mips/lib/crypto/ " Eric Biggers
2025-06-19 19:19 ` [PATCH v2 4/9] lib/crypto: powerpc: move arch/powerpc/lib/crypto/ " Eric Biggers
2025-06-19 19:19 ` [PATCH v2 5/9] lib/crypto: riscv: move arch/riscv/lib/crypto/ " Eric Biggers
2025-06-23 23:23   ` Palmer Dabbelt
2025-06-24  2:44     ` Eric Biggers
2025-06-19 19:19 ` [PATCH v2 6/9] lib/crypto: s390: move arch/s390/lib/crypto/ " Eric Biggers
2025-06-19 19:19 ` [PATCH v2 7/9] lib/crypto: sparc: move arch/sparc/lib/crypto/ " Eric Biggers
2025-06-19 19:19 ` [PATCH v2 8/9] lib/crypto: x86: move arch/x86/lib/crypto/ " Eric Biggers
2025-06-19 19:19 ` Eric Biggers [this message]
2025-06-20 21:29 ` [PATCH v2 0/9] lib/crypto: move arch/$(ARCH)/lib/crypto/ to lib/crypto/$(ARCH)/ Eric Biggers
2025-06-20 21:39 ` Ard Biesheuvel
2025-06-20 22:41 ` Sohil Mehta
2025-06-21  2:53 ` Martin K. Petersen

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=20250619191908.134235-10-ebiggers@kernel.org \
    --to=ebiggers@kernel.org \
    --cc=Jason@zx2c4.com \
    --cc=ardb@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=sparclinux@vger.kernel.org \
    --cc=x86@kernel.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 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).