From: patchwork-bot+netdevbpf@kernel.org
To: Alex Elder <elder@linaro.org>
Cc: davem@davemloft.net, kuba@kernel.org, rdunlap@infradead.org,
bjorn.andersson@linaro.org, mka@chromium.org,
evgreen@chromium.org, cpratapa@codeaurora.org,
avuyyuru@codeaurora.org, jponduru@codeaurora.org,
subashab@codeaurora.org, elder@kernel.org,
netdev@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: ipa: fix a build dependency
Date: Mon, 28 Feb 2022 11:50:10 +0000 [thread overview]
Message-ID: <164604901029.16787.14124027324200684971.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220225201530.182085-1-elder@linaro.org>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 25 Feb 2022 14:15:30 -0600 you wrote:
> An IPA build problem arose in the linux-next tree the other day.
> The problem is that a recent commit adds a new dependency on some
> code, and the Kconfig file for IPA doesn't reflect that dependency.
> As a result, some configurations can fail to build (particularly
> when COMPILE_TEST is enabled).
>
> The recent patch adds calls to qmp_get(), qmp_put(), and qmp_send(),
> and those are built based on the QCOM_AOSS_QMP config option. If
> that symbol is not defined, stubs are defined, so we just need to
> ensure QCOM_AOSS_QMP is compatible with QCOM_IPA, or it's not
> defined.
>
> [...]
Here is the summary with links:
- [net] net: ipa: fix a build dependency
https://git.kernel.org/netdev/net/c/caef14b7530c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-02-28 11:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 20:15 [PATCH net] net: ipa: fix a build dependency Alex Elder
2022-02-25 20:52 ` Randy Dunlap
2022-02-28 11:50 ` patchwork-bot+netdevbpf [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=164604901029.16787.14124027324200684971.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=avuyyuru@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=cpratapa@codeaurora.org \
--cc=davem@davemloft.net \
--cc=elder@kernel.org \
--cc=elder@linaro.org \
--cc=evgreen@chromium.org \
--cc=jponduru@codeaurora.org \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@chromium.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=subashab@codeaurora.org \
/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