From: David Lechner <dlechner@baylibre.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
David Lechner <dlechner@baylibre.com>,
kernel test robot <lkp@intel.com>
Subject: [PATCH] spi: axi-spi-engine: fix missing bitfield include
Date: Thu, 6 Feb 2025 15:55:13 -0600 [thread overview]
Message-ID: <20250206215513.2842270-1-dlechner@baylibre.com> (raw)
Fix missing linux/bitfield.h include needed for FIELD_GET macro.
Reported-by: kernel test robot <lkp@intel.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202502031224.wvHipe06-lkp@intel.com/
Closes: https://lore.kernel.org/oe-kbuild-all/202502031250.64gElGDs-lkp@intel.com/
Signed-off-by: David Lechner <dlechner@baylibre.com>
---
Hi Mark,
I know you prefer patches like this to fix something in a patch that has
already been applied, but it doesn't look like you actually picked up the
offending commit[1] yet in your main tree, so I don't have a commit hash
for a proper Fixes: tag.
Do you want a fix like this or should I send a v8 with the fix squashed?
[1]: https://lore.kernel.org/linux-spi/20250113-dlech-mainline-spi-engine-offload-2-v7-7-e0860c81caae@baylibre.com/
---
drivers/spi/spi-axi-spi-engine.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/spi/spi-axi-spi-engine.c b/drivers/spi/spi-axi-spi-engine.c
index dd6077d3ff7b..da9840957778 100644
--- a/drivers/spi/spi-axi-spi-engine.c
+++ b/drivers/spi/spi-axi-spi-engine.c
@@ -6,6 +6,7 @@
* Author: Lars-Peter Clausen <lars@metafoo.de>
*/
+#include <linux/bitfield.h>
#include <linux/bitops.h>
#include <linux/clk.h>
#include <linux/completion.h>
--
2.43.0
next reply other threads:[~2025-02-06 21:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 21:55 David Lechner [this message]
2025-02-07 13:36 ` [PATCH] spi: axi-spi-engine: fix missing bitfield include Mark Brown
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=20250206215513.2842270-1-dlechner@baylibre.com \
--to=dlechner@baylibre.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=lkp@intel.com \
/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