From: Alex Elder <elder@linaro.org>
To: Nick Desaulniers <ndesaulniers@google.com>,
Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>
Cc: arnd@arndb.de, bjorn.andersson@linaro.org, davem@davemloft.net,
johannes@sipsolutions.net, kuba@kernel.org,
linux-kernel@vger.kernel.org, masahiroy@kernel.org,
natechancellor@gmail.com, netdev@vger.kernel.org,
viro@zeniv.linux.org.uk
Subject: Re: [PATCH v3] bitfield.h: add FIELD_MAX() and field_max()
Date: Wed, 1 Apr 2020 13:24:14 -0500 [thread overview]
Message-ID: <3659efd7-4e72-6bff-5657-c1270e8553f4@linaro.org> (raw)
In-Reply-To: <20200401173515.142249-1-ndesaulniers@google.com>
On 4/1/20 12:35 PM, Nick Desaulniers wrote:
>> Define FIELD_MAX(), which supplies the maximum value that can be
>> represented by a field value. Define field_max() as well, to go
>> along with the lower-case forms of the field mask functions.
>>
>> Signed-off-by: Alex Elder <elder@linaro.org>
>> Acked-by: Jakub Kicinski <kuba@kernel.org>
>> ---
>> v3: Rebased on latest netdev-next/master.
>>
>> David, please take this into net-next as soon as possible. When the
>> IPA code was merged the other day this prerequisite patch was not
>> included, and as a result the IPA driver fails to build. Thank you.
>>
>> See: https://lkml.org/lkml/2020/3/10/1839
>>
>> -Alex
>
> In particular, this seems to now have regressed into mainline for the 5.7
> merge window as reported by Linaro's ToolChain Working Group's CI.
> Link: https://github.com/ClangBuiltLinux/linux/issues/963
Is the problem you're referring to the result of a build done
in the midst of a bisect?
The fix for this build error is currently present in the
torvalds/linux.git master branch:
6fcd42242ebc soc: qcom: ipa: kill IPA_RX_BUFFER_ORDER
I may be mistaken, but I believe this is the same problem I discussed
with Maxim Kuvyrkov this morning. A different build problem led to
an automated bisect, which conluded this was the cause because it
landed somewhere between the initial pull of the IPA code and the fix
I reference above.
-Alex
next prev parent reply other threads:[~2020-04-01 18:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 2:42 Alex Elder
2020-04-01 17:35 ` Nick Desaulniers
2020-04-01 18:24 ` Alex Elder [this message]
2020-04-01 19:13 ` Nick Desaulniers
2020-04-01 19:44 ` Alex Elder
2020-04-01 19:54 ` Nick Desaulniers
2020-04-01 20:21 ` Alex Elder
2020-04-01 22:26 ` Nick Desaulniers
2020-04-01 23:18 ` Alex Elder
2020-04-02 0:26 ` Nick Desaulniers
2020-04-02 7:58 ` Maxim Kuvyrkov
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=3659efd7-4e72-6bff-5657-c1270e8553f4@linaro.org \
--to=elder@linaro.org \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@linaro.org \
--cc=davem@davemloft.net \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=maxim.kuvyrkov@linaro.org \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=netdev@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®