From: Michal Simek <monstr@monstr.eu>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: linux-kernel@vger.kernel.org, microblaze-uclinux@itee.uq.edu.au
Subject: Re: [PATCH] microblaze: remove unused HAVE_ARCH_PCI_SET_DMA_MASK
Date: Mon, 12 Jul 2010 15:07:26 +0200 [thread overview]
Message-ID: <4C3B138E.4080208@monstr.eu> (raw)
In-Reply-To: <20100712153701V.fujita.tomonori@lab.ntt.co.jp>
FUJITA Tomonori wrote:
> HAVE_ARCH_PCI_SET_DMA_MASK was removed in 2.6.36 (no architecture has
> the own implementation of pci_set_dma_mask).
Added to next branch. I also fixed that kernel version.
Thanks,
Michal
>
> Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
> ---
> arch/microblaze/include/asm/dma-mapping.h | 6 ------
> 1 files changed, 0 insertions(+), 6 deletions(-)
>
> diff --git a/arch/microblaze/include/asm/dma-mapping.h b/arch/microblaze/include/asm/dma-mapping.h
> index 18b3731..5073895 100644
> --- a/arch/microblaze/include/asm/dma-mapping.h
> +++ b/arch/microblaze/include/asm/dma-mapping.h
> @@ -79,12 +79,6 @@ static inline int dma_supported(struct device *dev, u64 mask)
> return ops->dma_supported(dev, mask);
> }
>
> -#ifdef CONFIG_PCI
> -/* We have our own implementation of pci_set_dma_mask() */
> -#define HAVE_ARCH_PCI_SET_DMA_MASK
> -
> -#endif
> -
> static inline int dma_set_mask(struct device *dev, u64 dma_mask)
> {
> struct dma_map_ops *ops = get_dma_ops(dev);
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
prev parent reply other threads:[~2010-07-12 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 6:37 [PATCH] microblaze: remove unused HAVE_ARCH_PCI_SET_DMA_MASK FUJITA Tomonori
2010-07-12 6:39 ` FUJITA Tomonori
2010-07-12 13:07 ` Michal Simek [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=4C3B138E.4080208@monstr.eu \
--to=monstr@monstr.eu \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=microblaze-uclinux@itee.uq.edu.au \
/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