All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: akpm@linux-foundation.org, broonie@kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, linux-next@vger.kernel.org, mhocko@suse.cz,
	mm-commits@vger.kernel.org, sfr@canb.auug.org.au,
	linux-pci <linux-pci@vger.kernel.org>,
	Vidya Sagar <vidyas@nvidia.com>
Subject: Re: mmotm 2020-03-23-21-29 uploaded (pci/controller/dwc/pcie-tegra194.c)
Date: Tue, 24 Mar 2020 11:18:51 -0500	[thread overview]
Message-ID: <20200324161851.GA2300@google.com> (raw)
In-Reply-To: <62819368-150e-6b49-3ab3-9a2ab28481b3@infradead.org>

On Tue, Mar 24, 2020 at 08:16:34AM -0700, Randy Dunlap wrote:
> On 3/23/20 9:30 PM, akpm@linux-foundation.org wrote:
> > The mm-of-the-moment snapshot 2020-03-23-21-29 has been uploaded to
> > 
> >    http://www.ozlabs.org/~akpm/mmotm/
> > 
> > mmotm-readme.txt says
> > 
> > README for mm-of-the-moment:
> > 
> > http://www.ozlabs.org/~akpm/mmotm/
> > 
> > This is a snapshot of my -mm patch queue.  Uploaded at random hopefully
> > more than once a week.
> > 
> > You will need quilt to apply these patches to the latest Linus release (5.x
> > or 5.x-rcY).  The series file is in broken-out.tar.gz and is duplicated in
> > http://ozlabs.org/~akpm/mmotm/series
> 
> 
> on x86_64:
> 
> ../drivers/pci/controller/dwc/pcie-tegra194.c: In function ‘tegra_pcie_dw_parse_dt’:
> ../drivers/pci/controller/dwc/pcie-tegra194.c:1160:24: error: implicit declaration of function ‘devm_gpiod_get’; did you mean ‘devm_phy_get’? [-Werror=implicit-function-declaration]
>   pcie->pex_rst_gpiod = devm_gpiod_get(pcie->dev, "reset", GPIOD_IN);
>                         ^~~~~~~~~~~~~~
>                         devm_phy_get

Thanks a lot for the report!

This was found on mmotm, but I updated my -next branch with Lorenzo's
latest pci/endpoint branch (current head 775d9e68f470) and reproduced
this build failure with the .config you attached.

I dropped that branch from my -next branch for now and pushed it.

Bjorn

  reply	other threads:[~2020-03-24 16:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-24  4:30 mmotm 2020-03-23-21-29 uploaded akpm
2020-03-24 15:16 ` mmotm 2020-03-23-21-29 uploaded (pci/controller/dwc/pcie-tegra194.c) Randy Dunlap
2020-03-24 16:18   ` Bjorn Helgaas [this message]
2020-03-25 15:13     ` Vidya Sagar
2020-03-25 15:52       ` Randy Dunlap
2020-03-25 17:01       ` Lorenzo Pieralisi
2020-03-25 21:20         ` Bjorn Helgaas
2020-03-25 21:34           ` Randy Dunlap

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=20200324161851.GA2300@google.com \
    --to=helgaas@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mhocko@suse.cz \
    --cc=mm-commits@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    --cc=vidyas@nvidia.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.