From: Gal Pressman <gal@nvidia.com>
To: "Sudip Mukherjee (Codethink)" <sudipm.mukherjee@gmail.com>,
Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>
Cc: Alexander Aring <alex.aring@gmail.com>,
Stefan Schmidt <stefan@datenfreihafen.org>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
linux-wpan@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: build failure of next-20220830 due to 9c5d03d36251 ("genetlink: start to validate reserved header bytes")
Date: Tue, 30 Aug 2022 13:19:06 +0300 [thread overview]
Message-ID: <09270720-bc55-29e5-2310-980cabb444f4@nvidia.com> (raw)
In-Reply-To: <Yw3X1cB1j+r8uj7W@debian>
On 30/08/2022 12:26, Sudip Mukherjee (Codethink) wrote:
> Hi All,
>
> The builds of arm pxa_defconfig have failed to build next-20220830 with
> the error:
>
> net/ieee802154/nl802154.c:2503:26: error: 'NL802154_CMD_DEL_SEC_LEVEL' undeclared here (not in a function); did you mean 'NL802154_CMD_SET_CCA_ED_LEVEL'?
> 2503 | .resv_start_op = NL802154_CMD_DEL_SEC_LEVEL + 1,
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~
> | NL802154_CMD_SET_CCA_ED_LEVEL
>
> git bisect pointed to 9c5d03d36251 ("genetlink: start to validate reserved header bytes")
>
> I will be happy to test any patch or provide any extra log if needed.
>
>
I posted a fix:
https://lore.kernel.org/netdev/20220830101237.22782-1-gal@nvidia.com/
next prev parent reply other threads:[~2022-08-30 10:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 9:26 build failure of next-20220830 due to 9c5d03d36251 ("genetlink: start to validate reserved header bytes") Sudip Mukherjee (Codethink)
2022-08-30 10:19 ` Gal Pressman [this message]
2022-08-30 11:49 ` Sudip Mukherjee
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=09270720-bc55-29e5-2310-980cabb444f4@nvidia.com \
--to=gal@nvidia.com \
--cc=alex.aring@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stefan@datenfreihafen.org \
--cc=sudipm.mukherjee@gmail.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