From: Alex Elder <elder@linaro.org>
To: Jakub Kicinski <kuba@kernel.org>,
Nathan Chancellor <natechancellor@gmail.com>
Cc: David Miller <davem@davemloft.net>,
Al Viro <viro@zeniv.linux.org.uk>,
Johannes Berg <johannes@sipsolutions.net>,
Arnd Bergmann <arnd@arndb.de>,
Masahiro Yamada <masahiroy@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] bitfield.h: add FIELD_MAX() and field_max()
Date: Tue, 10 Mar 2020 21:45:43 -0500 [thread overview]
Message-ID: <e46a1ba6-e169-e5b5-7933-ab22848407df@linaro.org> (raw)
In-Reply-To: <bc50d249-60ab-767d-ae0c-02629483df34@linaro.org>
On 3/10/20 8:48 PM, Alex Elder wrote:
> On 3/10/20 4:58 PM, Jakub Kicinski wrote:
>> On Tue, 10 Mar 2020 14:29:38 -0700 Nathan Chancellor wrote:
>>> Without this patch, the IPA driver that was picked up a couple of days
>>> ago does not build...
>>
>> 😳
>>
>> Yes please, Alex could you repost ASAP with [PATCH net-next] subject
>> and CC netdev to get it into the netdev patchwork?
>>
>> Please also make IPA:
>>
>> depends on (ARCH_QCOM || COMPILE_TEST) && 64BIT && NET
>>
>> Otherwise it's really hard to make sure the code builds.
>
> Sorry all. I have been on vacation the last few days and only now
> saw this.
>
> I will put this together shortly.
I just sent an updated version of the field_max() patch. I will do
the COMPILE_TEST change separately (and not today).
-Alex
> -Alex
>
prev parent reply other threads:[~2020-03-11 2:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 4:23 [PATCH v2] bitfield.h: add FIELD_MAX() and field_max() Alex Elder
2020-03-10 21:29 ` Nathan Chancellor
2020-03-10 21:58 ` Jakub Kicinski
2020-03-11 1:48 ` Alex Elder
2020-03-11 2:45 ` Alex Elder [this message]
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=e46a1ba6-e169-e5b5-7933-ab22848407df@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=natechancellor@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).