[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <54520ABC.3040305@imgtec.com>
Date: Thu, 30 Oct 2014 09:54:04 +0000
From: Markos Chandras <Markos.Chandras@...tec.com>
To: James Hogan <james.hogan@...tec.com>,
Leonid Yegoshin <Leonid.Yegoshin@...tec.com>,
<linux-mips@...ux-mips.org>, <nbd@...nwrt.org>, <yanh@...ote.com>,
<linux-kernel@...r.kernel.org>, <ralf@...ux-mips.org>,
<alex.smith@...tec.com>, <taohl@...ote.com>, <chenhc@...ote.com>,
<blogic@...nwrt.org>
Subject: Re: [PATCH] MIPS: DMA: fix coherent alloc in non-coherent systems
On 10/30/2014 09:51 AM, James Hogan wrote:
> Hi Markos,
>
> On 30/10/14 09:48, Markos Chandras wrote:
>>> diff --git a/arch/mips/include/asm/mach-cavium-octeon/dma-coherence.h b/arch/mips/include/asm/mach-cavium-octeon/dma-coherence.h
>>> index f9f4486..fe0b465 100644
>>> --- a/arch/mips/include/asm/mach-cavium-octeon/dma-coherence.h
>>> +++ b/arch/mips/include/asm/mach-cavium-octeon/dma-coherence.h
>>> @@ -52,7 +52,7 @@ static inline int plat_dma_supported(struct device *dev, u64 mask)
>>> return 0;
>>> }
>>>
>>> -static inline int plat_device_is_coherent(struct device *dev)
>>> +static inline int plat_device_is_coherent(const struct device *dev)
>>
>> Why adding const here?
>>
>
> <snip>
>
>> Is it just a matter of consistence with the rest of the interfaces? Do
>> you need to move these into a separate patch since they don't quite fit
>> here.
>
> See the new new call to plat_device_is_coherent(), which passes dev,
> which is const.
>
> Cheers
> James
>
Ah yes you are right. Thanks!
--
markos
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists