All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Marc Zyngier <maz@kernel.org>
Cc: Samuel Holland <samuel@sholland.org>,
	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 irqchip tree
Date: Fri, 8 Jul 2022 14:13:44 +1000	[thread overview]
Message-ID: <20220708141344.3b521664@canb.auug.org.au> (raw)

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

Hi all,

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

drivers/pci/controller/pci-hyperv.c: In function 'hv_compose_msi_req_v2':
drivers/pci/controller/pci-hyperv.c:1654:42: error: passing argument 1 of 'hv_compose_msi_req_get_cpu' discards 'const' qualifier from pointer target type [-Werror=discarded-qualifiers]
 1654 |         cpu = hv_compose_msi_req_get_cpu(affinity);
      |                                          ^~~~~~~~
drivers/pci/controller/pci-hyperv.c:1638:55: note: expected 'struct cpumask *' but argument is of type 'const struct cpumask *'
 1638 | static int hv_compose_msi_req_get_cpu(struct cpumask *affinity)
      |                                       ~~~~~~~~~~~~~~~~^~~~~~~~
drivers/pci/controller/pci-hyperv.c: In function 'hv_compose_msi_req_v3':
drivers/pci/controller/pci-hyperv.c:1674:42: error: passing argument 1 of 'hv_compose_msi_req_get_cpu' discards 'const' qualifier from pointer target type [-Werror=discarded-qualifiers]
 1674 |         cpu = hv_compose_msi_req_get_cpu(affinity);
      |                                          ^~~~~~~~
drivers/pci/controller/pci-hyperv.c:1638:55: note: expected 'struct cpumask *' but argument is of type 'const struct cpumask *'
 1638 | static int hv_compose_msi_req_get_cpu(struct cpumask *affinity)
      |                                       ~~~~~~~~~~~~~~~~^~~~~~~~
cc1: all warnings being treated as errors

Caused by commit

  4d0b8298818b ("genirq: Return a const cpumask from irq_data_get_affinity_mask")

I have used the irqchip tree from next-20220707 for today.

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2022-07-08  4:13 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-08  4:13 Stephen Rothwell [this message]
2022-07-08  7:48 ` linux-next: build failure after merge of the irqchip tree Marc Zyngier
  -- strict thread matches above, loose matches on Subject: below --
2022-09-29 14:31 broonie
2022-09-29 14:31 ` broonie
2022-09-29 14:40 ` Robin Murphy
2022-09-29 14:40   ` Robin Murphy
2022-09-29 16:22   ` Marc Zyngier
2022-09-29 16:22     ` Marc Zyngier
2022-07-11  5:42 Stephen Rothwell
2022-07-11  8:15 ` Marc Zyngier
2021-06-22  4:15 Stephen Rothwell
2021-06-22  4:15 ` Stephen Rothwell
2021-04-08  6:35 Stephen Rothwell
2021-04-08  7:56 ` Marc Zyngier
2021-04-08  8:35   ` Jonathan Neuschäfer
2020-03-23  6:59 Stephen Rothwell
2020-03-23  8:08 ` Michal Simek
2020-03-26  6:36 ` Stephen Rothwell
2020-03-26  7:06   ` Michal Simek
2018-10-08  3:06 Stephen Rothwell
2018-10-08  7:06 ` Marc Zyngier
2015-04-13  7:05 Stephen Rothwell
2015-04-13  9:10 ` Stefan Agner
2015-04-13 10:50 ` Jason Cooper

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=20220708141344.3b521664@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=samuel@sholland.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.