All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-arm-msm@kernel.org
To: Nathan Chancellor <natechancellor@gmail.com>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] dmaengine: qcom: Always inline gpi_update_reg
Date: Mon, 01 Mar 2021 19:59:43 +0000	[thread overview]
Message-ID: <161462878380.6187.7974031409607934277.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210112191214.1264793-1-natechancellor@gmail.com>

Hello:

This patch was applied to qcom/linux.git (refs/heads/for-next):

On Tue, 12 Jan 2021 12:12:14 -0700 you wrote:
> When building with CONFIG_UBSAN_UNSIGNED_OVERFLOW, clang decides not to
> inline gpi_update_reg, which causes a linkage failure around __bad_mask:
> 
> ld.lld: error: undefined symbol: __bad_mask
> >>> referenced by bitfield.h:119 (include/linux/bitfield.h:119)
> >>>               dma/qcom/gpi.o:(gpi_update_reg) in archive drivers/built-in.a
> >>> referenced by bitfield.h:119 (include/linux/bitfield.h:119)
> >>>               dma/qcom/gpi.o:(gpi_update_reg) in archive drivers/built-in.a
> 
> [...]

Here is the summary with links:
  - dmaengine: qcom: Always inline gpi_update_reg
    https://git.kernel.org/qcom/c/0a6d3038d914

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2021-03-01 20:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-12 19:12 [PATCH] dmaengine: qcom: Always inline gpi_update_reg Nathan Chancellor
2021-01-13 11:21 ` Vinod Koul
2021-03-01 19:59 ` patchwork-bot+linux-arm-msm [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=161462878380.6187.7974031409607934277.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-arm-msm@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=natechancellor@gmail.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 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.