netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Elder <elder@linaro.org>
To: David Miller <davem@davemloft.net>
Cc: kuba@kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] soc: qcom: ipa: build IPA when COMPILE_TEST is enabled
Date: Fri, 13 Mar 2020 13:29:14 -0500	[thread overview]
Message-ID: <f886a27f-e7ff-3ad9-01ba-6b9fb0045b41@linaro.org> (raw)
In-Reply-To: <20200313.112524.278974546399568453.davem@davemloft.net>

On 3/13/20 1:25 PM, David Miller wrote:
> From: Alex Elder <elder@linaro.org>
> Date: Fri, 13 Mar 2020 07:11:26 -0500
> 
>> Make CONFIG_QCOM_IPA optionally dependent on CONFIG_COMPILE_TEST.
>>
>> Suggested-by: Jakub Kicinski <kuba@kernel.org>
>> Signed-off-by: Alex Elder <elder@linaro.org>
>> ---
>>
>> David, this implements a suggestion made by Jakub Kicinski.  I tested
>> it with GCC 9.2.1 for x86 and found no errors or warnings in the IPA
>> code.  It is the last IPA change I plan to make for v5.7.
>>
>> Once reviewed and found acceptable, it should go through net-next.
> 
> When I try to use this I end up with the following Kconfig warnings:

I'm very sorry about that.  I'll look it over again and fix it.

I got another report today from LKFT saying that there's a different
problem when ARM64 is built 64KB pages.  I'll address both of them in
an update.

					-Alex
 
> WARNING: unmet direct dependencies detected for QCOM_SCM
>   Depends on [n]: ARM || ARM64
>   Selected by [m]:
>   - QCOM_MDT_LOADER [=m]
> 
> So this needs more work.
> 


      reply	other threads:[~2020-03-13 18:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-13 12:11 [PATCH] soc: qcom: ipa: build IPA when COMPILE_TEST is enabled Alex Elder
2020-03-13 18:25 ` David Miller
2020-03-13 18:29   ` 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=f886a27f-e7ff-3ad9-01ba-6b9fb0045b41@linaro.org \
    --to=elder@linaro.org \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).