From: Jakub Kicinski <kuba@kernel.org>
To: Alex Elder <elder@linaro.org>
Cc: davem@davemloft.net, bjorn.andersson@linaro.org,
agross@kernel.org, ohad@wizery.com, evgreen@chromium.org,
cpratapa@codeaurora.org, subashab@codeaurora.org,
netdev@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/4] net: ipa: support COMPILE_TEST
Date: Sat, 9 Jan 2021 13:53:42 -0800 [thread overview]
Message-ID: <20210109135342.2c31836d@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <20210107233404.17030-1-elder@linaro.org>
On Thu, 7 Jan 2021 17:34:00 -0600 Alex Elder wrote:
> This series adds the IPA driver as a possible target when
> the COMPILE_TEST configuration is enabled. Two small changes to
> dependent subsystems needed to be made for this to work.
>
> Version 2 of this series adds one more patch, which adds the
> declation of struct page to "gsi_trans.h". The Intel kernel test
> robot reported that this was a problem for the alpha build.
>
> David/Jakub, please take all four of these patches through the
> net-next tree if you find them acceptable.
Applied, thanks a lot for doing this!
next prev parent reply other threads:[~2021-01-09 21:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 23:34 [PATCH net-next 0/4] net: ipa: support COMPILE_TEST Alex Elder
2021-01-07 23:34 ` [PATCH net-next 1/4] remoteproc: qcom: expose types for COMPILE_TEST Alex Elder
2021-01-07 23:34 ` [PATCH net-next 2/4] soc: qcom: mdt_loader: define stubs " Alex Elder
2021-01-07 23:34 ` [PATCH net-next 3/4] net: ipa: declare the page pointer type in "gsi_trans.h" Alex Elder
2021-01-07 23:34 ` [PATCH net-next 4/4] net: ipa: support COMPILE_TEST Alex Elder
2021-01-08 0:25 ` Bjorn Andersson
2021-01-09 21:53 ` Jakub Kicinski [this message]
2021-03-01 19:59 ` [PATCH net-next 0/4] " patchwork-bot+linux-arm-msm
2021-03-11 23:32 ` patchwork-bot+linux-remoteproc
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=20210109135342.2c31836d@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
--to=kuba@kernel.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=cpratapa@codeaurora.org \
--cc=davem@davemloft.net \
--cc=elder@linaro.org \
--cc=evgreen@chromium.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ohad@wizery.com \
--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 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.