All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: fsverity@lists.linux.dev
Subject: Re: [PATCH] fsverity: explicitly include <linux/export.h>
Date: Mon, 16 Jun 2025 20:24:55 -0700	[thread overview]
Message-ID: <20250617032455.GA8289@sol> (raw)
In-Reply-To: <20250614221723.131827-1-ebiggers@kernel.org>

On Sat, Jun 14, 2025 at 03:17:23PM -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").
> 
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> ---
> 
> This patch applies to v6.16-rc1 and is targeting fsverity/for-next
> 
>  fs/verity/enable.c        | 1 +
>  fs/verity/measure.c       | 1 +
>  fs/verity/open.c          | 1 +
>  fs/verity/read_metadata.c | 1 +
>  fs/verity/verify.c        | 1 +
>  5 files changed, 5 insertions(+)

Applied to https://git.kernel.org/pub/scm/fs/fsverity/linux.git/log/?h=for-next

- Eric

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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-14 22:17 [PATCH] fsverity: explicitly include <linux/export.h> Eric Biggers
2025-06-17  3:24 ` 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=20250617032455.GA8289@sol \
    --to=ebiggers@kernel.org \
    --cc=fsverity@lists.linux.dev \
    /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.