All of lore.kernel.org
 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>
Subject: Re: [PATCH v2] lib/crypto: explicitly include <linux/export.h>
Date: Mon, 16 Jun 2025 20:26:39 -0700	[thread overview]
Message-ID: <20250617032639.GC8289@sol> (raw)
In-Reply-To: <20250613184814.50173-1-ebiggers@kernel.org>

On Fri, Jun 13, 2025 at 11:48:14AM -0700, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
> 
> Fix build warnings with W=1 that started appearing after
> commit a934a57a42f6 ("scripts/misc-check: check missing #include
> <linux/export.h> when W=1").
> 
> While at it, also sort the include lists alphabetically.  (Keep
> asm/irqflags.h last, as otherwise it doesn't build on alpha.)
> 
> This handles all of lib/crypto/, but not arch/*/lib/crypto/.  The
> exports in arch/*/lib/crypto/ will go away when the code is properly
> integrated into lib/crypto/ as planned.
> 
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> 
> v2: keep asm/irqflags.h last, to avoid build error on alpha
>     (https://lore.kernel.org/all/202506140001.CtqYqDPn-lkp@intel.com/)

Applied to https://git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git/log/?h=libcrypto-next

- Eric

      reply	other threads:[~2025-06-17  3:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-13 18:48 [PATCH v2] lib/crypto: explicitly include <linux/export.h> Eric Biggers
2025-06-17  3:26 ` Eric Biggers [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=20250617032639.GC8289@sol \
    --to=ebiggers@kernel.org \
    --cc=Jason@zx2c4.com \
    --cc=ardb@kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --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 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.