Le 20/07/2017 à 08:28, Matt Brown a écrit :
The cacheflush prototypes currently use start and stop values and each
call requires typecasting the address to an unsigned long.
This patch changes the cacheflush prototypes to follow the x86 style of
using a base and size values, with base being a
I've realised that changing the arguments for the cacheflush functions
is much more work than its worth, due to other archs using these
functions.
The next patch will just translate the asm cacheflush functions to c,
keeping the existing parameters.
So this won't have any effect on the drivers.
Geert Uytterhoeven writes:
> On Thu, Jul 20, 2017 at 1:43 PM, Michael Ellerman wrote:
>> Matt Brown writes:
>>> The cacheflush prototypes currently use start and stop values and each
>>> call requires typecasting the
On Thu, Jul 20, 2017 at 1:43 PM, Michael Ellerman wrote:
> Matt Brown writes:
>> The cacheflush prototypes currently use start and stop values and each
>> call requires typecasting the address to an unsigned long.
>> This patch changes the
Hi Matt,
Thanks for tackling this mess.
Matt Brown writes:
> The cacheflush prototypes currently use start and stop values and each
> call requires typecasting the address to an unsigned long.
> This patch changes the cacheflush prototypes to follow the x86 style of
On Thu, Jul 20, 2017 at 8:28 AM, Matt Brown wrote:
> The cacheflush prototypes currently use start and stop values and each
> call requires typecasting the address to an unsigned long.
> This patch changes the cacheflush prototypes to follow the x86 style of
> using a
The cacheflush prototypes currently use start and stop values and each
call requires typecasting the address to an unsigned long.
This patch changes the cacheflush prototypes to follow the x86 style of
using a base and size values, with base being a void pointer.
All callers of the cacheflush