From: Mark Brown <broonie@kernel.org>
To: Ludovic Barre <ludovic.Barre@st.com>
Cc: Marek Vasut <marek.vasut@gmail.com>,
Boris Brezillon <bbrezillon@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
linux-mtd@lists.infradead.org, linux-spi@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] spi: stm32-qspi: add spi_master_put in release function
Date: Mon, 25 Mar 2019 16:03:13 +0000 [thread overview]
Message-ID: <20190325160313.GJ7284@sirena.org.uk> (raw)
In-Reply-To: <1553265354-16433-2-git-send-email-ludovic.Barre@st.com>
[-- Attachment #1: Type: text/plain, Size: 556 bytes --]
On Fri, Mar 22, 2019 at 03:35:53PM +0100, Ludovic Barre wrote:
> From: Ludovic Barre <ludovic.barre@st.com>
>
> This patch adds spi_master_put in release function
> to drop the controller's refcount.
I'm getting build errors with this:
CC drivers/spi/spi-stm32-qspi.o
drivers/spi/spi-stm32-qspi.c: In function ‘stm32_qspi_probe’:
drivers/spi/spi-stm32-qspi.c:430:8: error: ‘struct stm32_qspi’ has no member named ‘phys_base’; did you mean ‘io_base’?
qspi->phys_base = res->start;
^~~~~~~~~
io_base
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-03-25 16:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 14:35 [PATCH 0/2] spi: stm32-qspi: add dma support Ludovic Barre
2019-03-22 14:35 ` [PATCH 1/2] spi: stm32-qspi: add spi_master_put in release function Ludovic Barre
2019-03-25 16:03 ` Mark Brown [this message]
2019-03-25 16:19 ` Ludovic BARRE
2019-03-22 14:35 ` [PATCH 2/2] spi: stm32-qspi: add dma support Ludovic Barre
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=20190325160313.GJ7284@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alexandre.torgue@st.com \
--cc=bbrezillon@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=ludovic.Barre@st.com \
--cc=marek.vasut@gmail.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh+dt@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).