linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dinh Nguyen <dinguyen@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org,
	Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
	kernel test robot <lkp@intel.com>,
	Richard Gong <richard.gong@linux.intel.com>
Subject: Re: [PATCHv2 RESEND] firmware: stratix10-svc: build only on 64-bit ARM
Date: Sun, 4 Apr 2021 10:20:26 -0500	[thread overview]
Message-ID: <943c4179-409d-24f5-4324-7f2242920cc5@kernel.org> (raw)
In-Reply-To: <YGnIdZ5mbTJnREGB@kroah.com>



On 4/4/21 9:08 AM, Greg KH wrote:
> On Sun, Apr 04, 2021 at 07:46:09AM -0500, Dinh Nguyen wrote:
>> From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
>>
>> The Stratix10 service layer and RCU drivers are useful only on
>> Stratix10, so on ARMv8.  Compile testing the RCU driver on 32-bit ARM
>> fails:
>>
>>    drivers/firmware/stratix10-rsu.c: In function 'rsu_status_callback':
>>    include/linux/compiler_types.h:320:38: error: call to '__compiletime_assert_179'
>>      declared with attribute error: FIELD_GET: type of reg too small for mask
>>      _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
>>    ...
>>    drivers/firmware/stratix10-rsu.c:96:26: note: in expansion of macro 'FIELD_GET'
>>      priv->status.version = FIELD_GET(RSU_VERSION_MASK,
>>
>> Fixes: 4483397b0353 ("ARM: socfpga: drop ARCH_SOCFPGA")
> 
> Where is this commit id?  I don't see it in Linus's tree, is it
> somewhere else?
> 

It's in the for-next branch in the soc tree. This patch fixes a patch 
that was just recently submitted by Krzysztof.

Dinh

  reply	other threads:[~2021-04-04 15:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-04 12:46 [PATCHv2 RESEND] firmware: stratix10-svc: build only on 64-bit ARM Dinh Nguyen
2021-04-04 14:08 ` Greg KH
2021-04-04 15:20   ` Dinh Nguyen [this message]
2021-04-05 10:30     ` Greg KH
2021-04-05 13:09       ` Dinh Nguyen

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=943c4179-409d-24f5-4324-7f2242920cc5@kernel.org \
    --to=dinguyen@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=krzysztof.kozlowski@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=richard.gong@linux.intel.com \
    /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).