linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Kishon Vijay Abraham I <kishon@ti.com>, Vinod Koul <vkoul@kernel.org>
Cc: Aswath Govindraju <a-govindraju@ti.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 phy-next tree
Date: Fri, 24 Dec 2021 14:03:02 +1100	[thread overview]
Message-ID: <20211224140302.33d25020@canb.auug.org.au> (raw)

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

Hi all,

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

drivers/phy/phy-can-transceiver.c: In function 'can_transceiver_phy_power_on':
drivers/phy/phy-can-transceiver.c:35:9: error: implicit declaration of function 'mux_state_select'; did you mean 'mux_control_select'? [-Werror=implicit-function-declaration]
   35 |   ret = mux_state_select(can_transceiver_phy->mux_state);
      |         ^~~~~~~~~~~~~~~~
      |         mux_control_select
drivers/phy/phy-can-transceiver.c: In function 'can_transceiver_phy_power_off':
drivers/phy/phy-can-transceiver.c:59:3: error: implicit declaration of function 'mux_state_deselect'; did you mean 'mux_control_deselect'? [-Werror=implicit-function-declaration]
   59 |   mux_state_deselect(can_transceiver_phy->mux_state);
      |   ^~~~~~~~~~~~~~~~~~
      |   mux_control_deselect
drivers/phy/phy-can-transceiver.c: In function 'can_transceiver_phy_probe':
drivers/phy/phy-can-transceiver.c:113:15: error: implicit declaration of function 'devm_mux_state_get'; did you mean 'devm_mux_control_get'? [-Werror=implicit-function-declaration]
  113 |   mux_state = devm_mux_state_get(dev, NULL);
      |               ^~~~~~~~~~~~~~~~~~
      |               devm_mux_control_get
drivers/phy/phy-can-transceiver.c:113:13: error: assignment to 'struct mux_state *' from 'int' makes pointer from integer without a cast [-Werror=int-conversion]
  113 |   mux_state = devm_mux_state_get(dev, NULL);
      |             ^
cc1: all warnings being treated as errors

Caused by commit

  1e68cd3ff73e ("phy: phy-can-transceiver: Add support for setting mux")

I have used the phy-next tree from next-20211223 for today.

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2021-12-24  3:03 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-24  3:03 Stephen Rothwell [this message]
2021-12-24  4:37 ` linux-next: build failure after merge of the phy-next tree Vinod Koul
  -- strict thread matches above, loose matches on Subject: below --
2023-08-18  5:40 Stephen Rothwell
2023-08-22 14:00 ` Vinod Koul
2023-02-13  2:55 Stephen Rothwell
2023-02-13  5:17 ` Vinod Koul
2022-07-07  5:39 Stephen Rothwell
2022-07-07  5:53 ` Vinod Koul
2021-12-15 13:49 broonie
2021-12-15 14:14 ` Marcel Ziswiler
2021-12-15 15:20   ` Vinod Koul
2020-12-01  6:07 Stephen Rothwell
2020-12-01  6:45 ` Sergio Paracuellos
2020-12-01 10:39   ` Vinod Koul
2020-11-17  2:40 Stephen Rothwell
2020-11-17 10:00 ` Vinod Koul
2020-11-18  2:56   ` Stephen Rothwell
2020-11-18  4:23     ` Vinod Koul
2019-08-27  5:50 Stephen Rothwell
2017-03-30  3:47 Stephen Rothwell
2017-03-30  5:39 ` Kishon Vijay Abraham I

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=20211224140302.33d25020@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=a-govindraju@ti.com \
    --cc=kishon@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=vkoul@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).