mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kees Cook <kees@kernel.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-kernel@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>,
	kunit-dev@googlegroups.com
Subject: Re: [PATCH] MAINTAINERS: add crc_kunit.c back to CRC LIBRARY
Date: Mon, 12 May 2025 13:44:59 -0700	[thread overview]
Message-ID: <202505121344.4ED1902A1@keescook> (raw)
In-Reply-To: <20250511052151.420228-1-ebiggers@kernel.org>

On Sat, May 10, 2025 at 10:21:51PM -0700, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
> 
> Restore lib/tests/crc_kunit.c to CRC LIBRARY following the rename in
> commit db6fe4d61ece ("lib: Move KUnit tests into tests/ subdirectory")
> which made it no longer match the file pattern lib/crc*.
> 
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> ---
> 
> I'm planning to take this patch via the crc tree.

Oops, thanks!

Reviewed-by: Kees Cook <kees@kernel.org>

-Kees

> 
>  MAINTAINERS | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index c59316109e3f8..ac70e19c53cfd 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -6251,10 +6251,11 @@ S:	Maintained
>  T:	git https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git crc-next
>  F:	Documentation/staging/crc*
>  F:	arch/*/lib/crc*
>  F:	include/linux/crc*
>  F:	lib/crc*
> +F:	lib/tests/crc_kunit.c
>  F:	scripts/gen-crc-consts.py
>  
>  CREATIVE SB0540
>  M:	Bastien Nocera <hadess@hadess.net>
>  L:	linux-input@vger.kernel.org
> 
> base-commit: 46e3311607d6c18a760fba4afbd5d24d42abb0f3
> -- 
> 2.49.0
> 

-- 
Kees Cook

      reply	other threads:[~2025-05-12 20:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-11  5:21 Eric Biggers
2025-05-12 20:44 ` Kees Cook [this message]

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=202505121344.4ED1902A1@keescook \
    --to=kees@kernel.org \
    --cc=ardb@kernel.org \
    --cc=ebiggers@kernel.org \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®