[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <81dedbcc-14f6-f02f-2ce9-114d57c8d9d4@oracle.com>
Date: Fri, 19 Aug 2016 09:38:23 -0700
From: Santosh Shilimkar <santosh.shilimkar@...cle.com>
To: Roger Quadros <rogerq@...com>,
Russell King - ARM Linux <linux@...linux.org.uk>
Cc: ssantosh@...nel.org, grygorii.strashko@...com,
linux-arm-kernel@...ts.infradead.org, linux-usb@...r.kernel.org,
linux-kernel@...r.kernel.org, stable@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Arnd Bergmann <arnd@...db.de>, Olof Johansson <olof@...om.net>,
Catalin Marinas <catalin.marinas@....com>,
Linus Walleij <linus.walleij@...aro.org>
Subject: Re: [PATCH 1/1] ARM: dma: fix dma_max_pfn()
On 8/19/2016 12:30 AM, Roger Quadros wrote:
> Hi Santosh,
>
>>> So I'm 99.9% convinced that the proposed change is correct.
>>>
>> I will got with that then :-) and take my objection back. Just
>> saying that if there other breakages which I can't recollect now,
>> those drivers needs to be patched as well.
>>
> I was able to boot the Keystone2 Edison EVM over NFS with the $subject patch.
> Boot log is below. Do you see anything suspicious?
>
Logs looks ok to me. Probably do some tests where DMA and bounce buffers
etc gets tested. Running it through your internal regression
suit will be good idea as well if thats possible.
Regards,
Santosh
Powered by blists - more mailing lists