linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Vinod Koul <vkoul@kernel.org>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
	Yejune Deng <yejune.deng@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the phy-next tree
Date: Wed, 18 Nov 2020 13:56:19 +1100	[thread overview]
Message-ID: <20201118135619.4a4bf4c5@canb.auug.org.au> (raw)
In-Reply-To: <20201117100056.GF50232@vkoul-mobl>

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

Hi Vinod,

On Tue, 17 Nov 2020 15:30:56 +0530 Vinod Koul <vkoul@kernel.org> wrote:
>
> On 17-11-20, 13:40, Stephen Rothwell wrote:
> > Hi all,
> > 
> > After merging the phy-next tree, today's linux-next build (arm
> > multi_v7_defconfig) failed like this:
> > 
> > drivers/soc/amlogic/meson-ee-pwrc.c: In function 'meson_ee_pwrc_init_domain':
> > drivers/soc/amlogic/meson-ee-pwrc.c:416:65: error: expected ';' before 'if'
> >   416 |   dom->rstc = devm_reset_control_array_get_exclusive(&pdev->dev)
> >       |                                                                 ^
> >       |                                                                 ;
> >   417 |   if (IS_ERR(dom->rstc))
> >       |   ~~                                                             
> > 
> > Caused by commit
> > 
> >   3cc8e86721ad ("phy: amlogic: Replace devm_reset_control_array_get()")
> > 
> > I have used the phy-next tree from next-20201116 for today.  
> 
> I have reverted this commit

Thanks, but forgot to push out?

-- 
Cheers,
Stephen Rothwell

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

  reply	other threads:[~2020-11-18  2:56 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-17  2:40 linux-next: build failure after merge of the phy-next tree Stephen Rothwell
2020-11-17 10:00 ` Vinod Koul
2020-11-18  2:56   ` Stephen Rothwell [this message]
2020-11-18  4:23     ` 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-24  3:03 Stephen Rothwell
2021-12-24  4:37 ` 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
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=20201118135619.4a4bf4c5@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=kishon@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=vkoul@kernel.org \
    --cc=yejune.deng@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 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).