public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: Mukesh Kumar Savaliya <quic_msavaliy@quicinc.com>,
	Viken Dadhaniya <quic_vdadhani@quicinc.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the i2c-host tree
Date: Tue, 12 Mar 2024 10:41:27 +1100	[thread overview]
Message-ID: <20240312104127.3fb5e650@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 670 bytes --]

Hi all,

After merging the i2c-host tree, today's linux-next build (x86_64
allmodconfig) failed like this:

drivers/i2c/busses/i2c-qcom-geni.c: In function 'i2c_gpi_cb_result':
drivers/i2c/busses/i2c-qcom-geni.c:493:18: error: implicit declaration of function 'FIELD_GET' [-Werror=implicit-function-declaration]
  493 |         status = FIELD_GET(I2C_DMA_TX_IRQ_MASK, i2c_res->status);
      |                  ^~~~~~~~~
cc1: all warnings being treated as errors

Caused by commit

  313d6aa4c648 ("i2c: i2c-qcom-geni: Parse Error correctly in i2c GSI mode")

I have used the i2c-host tree from next-20240308 for today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2024-03-11 23:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-11 23:41 Stephen Rothwell [this message]
2024-03-12 10:44 ` linux-next: build failure after merge of the i2c-host tree Andi Shyti
  -- strict thread matches above, loose matches on Subject: below --
2024-05-22  0:41 Stephen Rothwell
2024-05-22  5:33 ` Heiner Kallweit
2024-05-28  0:52   ` Stephen Rothwell
2024-05-28  1:01 ` Stephen Rothwell
2025-05-06  9:11 Stephen Rothwell
2025-05-06 11:47 ` Andi Shyti
2025-07-04  2:02 Stephen Rothwell
2025-07-04  2:16 ` Qianfeng Rong
2025-07-04  2:36   ` Stephen Rothwell
2025-07-04  2:50     ` Qianfeng Rong

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=20240312104127.3fb5e650@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=andi.shyti@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=quic_msavaliy@quicinc.com \
    --cc=quic_vdadhani@quicinc.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