From: Florian Westphal <fw@strlen.de>
To: Fernando Fernandez Mancera <fmancera@suse.de>
Cc: kernel test robot <lkp@intel.com>,
netfilter-devel@vger.kernel.org, oe-kbuild-all@lists.linux.dev,
coreteam@netfilter.org, phil@nwl.cc, pablo@netfilter.org
Subject: Re: [PATCH nf-next v5] netfilter: nf_tables: add math expression support
Date: Mon, 27 Apr 2026 10:07:22 +0200 [thread overview]
Message-ID: <ae8ZM32SuUg2PTwV@strlen.de> (raw)
In-Reply-To: <e6315242-d34d-4a9a-824e-c9ebf0b03c83@suse.de>
Fernando Fernandez Mancera <fmancera@suse.de> wrote:
> On 4/26/26 5:57 AM, kernel test robot wrote:
> > Hi Fernando,
> >
> > kernel test robot noticed the following build errors:
> >
> > [auto build test ERROR on nf-next/master]
> >
> > url: https://github.com/intel-lab-lkp/linux/commits/Fernando-Fernandez-Mancera/netfilter-nf_tables-add-math-expression-support/20260424-055358
> > base: https://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf-next.git master
~~~~~~
> > | Reported-by: kernel test robot <lkp@intel.com>
> > | Closes: https://lore.kernel.org/oe-kbuild-all/202604261140.gX71SoJp-lkp@intel.com/
> >
>
> I am completely lost here. How is this happening? I do not see any of
> these errors locally with W=1.
Sure, you use main, not master. I'll remove master from the repository,
hopefully that will stop future reports like this.
> What? But I see:
>
> int nft_parse_register_load(const struct nft_ctx *ctx,
> const struct nlattr *attr, u8 *sreg, u32 len);
>
> Is this a bogus report?
Yes, wrong branch.
next prev parent reply other threads:[~2026-04-27 8:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 15:59 [PATCH nf-next v5] netfilter: nf_tables: add math expression support Fernando Fernandez Mancera
2026-04-26 3:57 ` kernel test robot
2026-04-27 7:26 ` Fernando Fernandez Mancera
2026-04-27 8:07 ` Florian Westphal [this message]
2026-04-27 14:07 ` Philip Li
2026-05-05 1:55 ` kernel test robot
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=ae8ZM32SuUg2PTwV@strlen.de \
--to=fw@strlen.de \
--cc=coreteam@netfilter.org \
--cc=fmancera@suse.de \
--cc=lkp@intel.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pablo@netfilter.org \
--cc=phil@nwl.cc \
/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.