From: Grant Likely <grant.likely@secretlab.ca>
To: Tomoya MORINAGA <tomoya.rohm@gmail.com>,
spi-devel-general@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Cc: qi.wang@intel.com, yong.y.wang@intel.com, joel.clark@intel.com,
kok.howg.ewe@intel.com, Wolfram Sang <w.sang@pengutronix.de>,
Tomoya MORINAGA <tomoya.rohm@gmail.com>
Subject: Re: [PATCH 1/4] spi-topcliff-pch: Modify pci-bus number dynamically to get DMA device info
Date: Fri, 09 Mar 2012 16:45:58 -0700 [thread overview]
Message-ID: <20120309234558.692513E093E@localhost> (raw)
In-Reply-To: <1323403905-3432-1-git-send-email-tomoya.rohm@gmail.com>
On Fri, 9 Dec 2011 13:11:42 +0900, Tomoya MORINAGA <tomoya.rohm@gmail.com> wrote:
> Signed-off-by: Tomoya MORINAGA <tomoya.rohm@gmail.com>
> ---
> drivers/spi/spi-topcliff-pch.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/spi/spi-topcliff-pch.c b/drivers/spi/spi-topcliff-pch.c
> index 99ec279..fcd9462 100644
> --- a/drivers/spi/spi-topcliff-pch.c
> +++ b/drivers/spi/spi-topcliff-pch.c
> @@ -920,7 +920,8 @@ static void pch_spi_request_dma(struct pch_spi_data *data, int bpw)
> dma_cap_set(DMA_SLAVE, mask);
>
> /* Get DMA's dev information */
> - dma_dev = pci_get_bus_and_slot(2, PCI_DEVFN(12, 0));
> + dma_dev = pci_get_bus_and_slot(data->board_dat->pdev->bus->number,
> + PCI_DEVFN(12, 0));
Applied, thanks
g.
prev parent reply other threads:[~2012-03-09 23:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 4:11 [PATCH 1/4] spi-topcliff-pch: Modify pci-bus number dynamically to get DMA device info Tomoya MORINAGA
[not found] ` <1323403905-3432-1-git-send-email-tomoya.rohm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-01-19 2:34 ` Tomoya MORINAGA
2012-01-19 2:34 ` Tomoya MORINAGA
[not found] ` <CANKRQniO55ZO+15Wt63Jtj4_MJk3b04_KXZT4bcrOaJjBedzyQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-03-09 23:50 ` Grant Likely
2012-03-09 23:50 ` Grant Likely
2012-03-09 23:45 ` Grant Likely [this message]
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=20120309234558.692513E093E@localhost \
--to=grant.likely@secretlab.ca \
--cc=joel.clark@intel.com \
--cc=kok.howg.ewe@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=qi.wang@intel.com \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=tomoya.rohm@gmail.com \
--cc=w.sang@pengutronix.de \
--cc=yong.y.wang@intel.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.