linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masahiro Yamada <masahiroy@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Jason A. Donenfeld" <Jason@zx2c4.com>
Subject: Re: linux-next: build failure after merge of the kbuild tree
Date: Tue, 7 Apr 2020 13:41:47 +0900	[thread overview]
Message-ID: <CAK7LNATjRY8RT4vAjhT=L0xJY2nnVHR2VdrkfZxTkFV2YC_iXQ@mail.gmail.com> (raw)
In-Reply-To: <20200406123403.4f20fbb1@canb.auug.org.au>

On Mon, Apr 6, 2020 at 11:34 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> After merging the kbuild tree, today's linux-next build (powercp
> allyesconfig) failed like this:
>
> In file included from net/netfilter/nft_set_pipapo.c:342:
> net/netfilter/nft_set_pipapo_avx2.h:4:10: fatal error: asm/fpu/xstate.h: No such file or directory
>     4 | #include <asm/fpu/xstate.h>
>       |          ^~~~~~~~~~~~~~~~~~
>
> Caused by commit
>
>   b851fc367202 ("x86: update AS_* macros to binutils >=2.23, supporting ADX and AVX2")
>
> I have reverted that commit for today.

I will fix as follows:


diff --git a/net/netfilter/nft_set_pipapo_avx2.h
b/net/netfilter/nft_set_pipapo_avx2.h
index 8467337c5f4c..a1cde35fdad6 100644
--- a/net/netfilter/nft_set_pipapo_avx2.h
+++ b/net/netfilter/nft_set_pipapo_avx2.h
@@ -1,6 +1,7 @@
 /* SPDX-License-Identifier: GPL-2.0-only */
 #ifndef _NFT_SET_PIPAPO_AVX2_H

+#ifdef CONFIG_X86_64
 #include <asm/fpu/xstate.h>
 #define NFT_PIPAPO_ALIGN       (XSAVE_YMM_SIZE / BITS_PER_BYTE)

@@ -8,4 +9,6 @@ bool nft_pipapo_avx2_lookup(const struct net *net,
const struct nft_set *set,
                            const u32 *key, const struct nft_set_ext **ext);
 bool nft_pipapo_avx2_estimate(const struct nft_set_desc *desc, u32 features,
                              struct nft_set_estimate *est);
+#endif /* CONFIG_X86_64 */
+
 #endif /* _NFT_SET_PIPAPO_AVX2_H */



-- 
Best Regards
Masahiro Yamada

  reply	other threads:[~2020-04-07  4:42 UTC|newest]

Thread overview: 91+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-06  2:34 linux-next: build failure after merge of the kbuild tree Stephen Rothwell
2020-04-07  4:41 ` Masahiro Yamada [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-08-18  4:01 Stephen Rothwell
2025-08-18  4:27 ` Nathan Chancellor
2025-07-30  6:12 Stephen Rothwell
2025-08-04  1:25 ` Stephen Rothwell
2025-08-04  7:09   ` Alexey Gladkov
2025-08-04 22:17     ` Stephen Rothwell
2025-08-05  3:33       ` Stephen Rothwell
2025-08-12 21:51         ` Alexey Gladkov
2025-06-03  6:39 Stephen Rothwell
2025-03-23 23:30 Stephen Rothwell
2025-03-24 13:52 ` Jeff Johnson
2025-03-24 17:37   ` Arnd Bergmann
2025-03-24 17:40     ` Jeff Johnson
2025-03-26 23:16 ` Stephen Rothwell
2025-03-27  0:20   ` Jeff Johnson
2025-03-27 10:13     ` Alessandro Carminati
2024-09-11  0:18 Stephen Rothwell
2024-09-11  9:38 ` Masahiro Yamada
2024-09-11 13:20   ` Kris Van Hees
2024-09-12  1:49     ` Masahiro Yamada
2022-10-14  1:42 Stephen Rothwell
2022-10-14 13:31 ` Masahiro Yamada
2022-10-12 22:17 Stephen Rothwell
2022-10-12 22:34 ` Masahiro Yamada
2022-10-12 23:51   ` Stephen Rothwell
2022-09-08 23:00 Stephen Rothwell
2022-09-09  5:10 ` Masahiro Yamada
2022-09-09  5:24   ` Stephen Rothwell
2022-09-09  6:13     ` Stephen Rothwell
2022-09-09  6:48       ` Masahiro Yamada
2022-09-09  7:49         ` Stephen Rothwell
     [not found]           ` <CAK7LNARiW66Hk5JJgRYb-edkb6sgTWPbNr1iETkq-RASCo-YkA@mail.gmail.com>
2022-09-11 23:55             ` Stephen Rothwell
2022-09-12  5:06               ` Masahiro Yamada
2022-09-12  7:43                 ` Stephen Rothwell
2022-09-09  8:26         ` Stephen Rothwell
2022-09-08  0:06 Stephen Rothwell
2022-09-08  4:14 ` Masahiro Yamada
2022-09-07 12:34 Stephen Rothwell
2022-09-07 13:49 ` Masahiro Yamada
2022-05-23 10:59 Stephen Rothwell
2022-05-23 15:59 ` Masahiro Yamada
2021-08-26  9:13 Stephen Rothwell
2021-08-27  0:52 ` Masahiro Yamada
2021-08-27  1:50   ` Stephen Rothwell
2021-08-27  2:49     ` Masahiro Yamada
2021-02-21 21:33 Stephen Rothwell
2021-02-21 23:21 ` Masahiro Yamada
2020-07-07  7:07 Stephen Rothwell
2020-07-13  1:56 ` Stephen Rothwell
2020-07-13  7:52   ` Masahiro Yamada
2020-03-10 22:53 Stephen Rothwell
2020-03-11  4:22 ` Masahiro Yamada
2019-07-16  4:31 Stephen Rothwell
2019-07-16  4:59 ` Masahiro Yamada
2019-07-16  6:42   ` Stephen Rothwell
2019-07-05  8:31 Stephen Rothwell
2019-07-06  0:05 ` Michael Kelley
2019-07-06  0:58   ` Masahiro Yamada
2019-05-05 23:46 Stephen Rothwell
2019-05-05 23:35 Stephen Rothwell
2019-05-05 22:40 Stephen Rothwell
2018-08-22 22:35 Stephen Rothwell
2018-08-23  9:03 ` Masahiro Yamada
2018-05-30  1:29 Stephen Rothwell
2018-05-30  1:44 ` Masahiro Yamada
2018-05-15  5:50 Stephen Rothwell
2018-05-16  6:01 ` Masahiro Yamada
2018-05-16  7:26   ` Stephen Rothwell
2018-05-17 13:45     ` Masahiro Yamada
2018-03-28 21:58 Stephen Rothwell
2018-03-29  1:59 ` Masahiro Yamada
2016-09-15  6:08 Stephen Rothwell
2016-09-22 12:52 ` Michal Marek
2016-07-28  2:08 Stephen Rothwell
2016-07-28  2:40 ` Michael Ellerman
2016-03-15 23:58 Stephen Rothwell
2016-03-16  7:53 ` Daniel Wagner
2016-03-16  7:56   ` Michal Marek
2016-03-16 11:29     ` Stephen Rothwell
2016-03-16 11:31       ` Michal Marek
2013-02-24 23:56 Stephen Rothwell
2013-02-25 10:28 ` Michal Marek
2013-02-25 10:58   ` Stephen Rothwell
2013-02-25 11:02     ` Stephen Rothwell
2013-02-25 11:36     ` Michal Marek
2011-04-19 22:25 Stephen Rothwell
2011-04-19 22:30 ` Stephen Rothwell
2011-04-20 13:50 ` Michal Marek
2010-03-11  5:15 Stephen Rothwell

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='CAK7LNATjRY8RT4vAjhT=L0xJY2nnVHR2VdrkfZxTkFV2YC_iXQ@mail.gmail.com' \
    --to=masahiroy@kernel.org \
    --cc=Jason@zx2c4.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).