On 4/2/20 5:43 PM, Frederic Barrat wrote:
> We can access the trigger page through standard APIs so let's use it
> and avoid saving it when allocating the interrupt. It will also allow
> to simplify allocation in a later patch.
>
> Signed-off-by: Frederic Barrat
Reviewed-by: Cédric Le Goater
On Thu, 2 Apr 2020 17:43:50 +0200
Frederic Barrat wrote:
> We can access the trigger page through standard APIs so let's use it
> and avoid saving it when allocating the interrupt. It will also allow
> to simplify allocation in a later patch.
>
> Signed-off-by: Frederic Barrat
> ---
Reviewed-
On 3/4/20 2:43 am, Frederic Barrat wrote:
We can access the trigger page through standard APIs so let's use it
and avoid saving it when allocating the interrupt. It will also allow
to simplify allocation in a later patch.
Signed-off-by: Frederic Barrat
I don't see any obvious issues.
Acked-b
We can access the trigger page through standard APIs so let's use it
and avoid saving it when allocating the interrupt. It will also allow
to simplify allocation in a later patch.
Signed-off-by: Frederic Barrat
---
drivers/misc/ocxl/afu_irq.c | 8 ++--
1 file changed, 6 insertions(+), 2 dele
