pt., 10 maj 2019 o 18:22 Anton Ivanov
napisał(a):
>
>
> On 10/05/2019 17:20, Bartosz Golaszewski wrote:
> > pt., 10 maj 2019 o 11:16 Bartosz Golaszewski napisał(a):
> >> śr., 8 maj 2019 o 09:13 Richard Weinberger napisał(a):
> >>> - Ursprüngliche Mail -
> > Can you please check?
>
On 10/05/2019 17:20, Bartosz Golaszewski wrote:
pt., 10 maj 2019 o 11:16 Bartosz Golaszewski napisał(a):
śr., 8 maj 2019 o 09:13 Richard Weinberger napisał(a):
- Ursprüngliche Mail -
Can you please check?
This patch is already queued in -next. So we need to decide whether to
pt., 10 maj 2019 o 11:16 Bartosz Golaszewski napisał(a):
>
> śr., 8 maj 2019 o 09:13 Richard Weinberger napisał(a):
> >
> > - Ursprüngliche Mail -
> > >> Can you please check?
> > >> This patch is already queued in -next. So we need to decide whether to
> > >> revert or fix it now.
> >
śr., 8 maj 2019 o 09:13 Richard Weinberger napisał(a):
>
> - Ursprüngliche Mail -
> >> Can you please check?
> >> This patch is already queued in -next. So we need to decide whether to
> >> revert or fix it now.
> >>
> > I am looking at it. It passed tests in my case (I did the usual
- Ursprüngliche Mail -
>> Can you please check?
>> This patch is already queued in -next. So we need to decide whether to
>> revert or fix it now.
>>
> I am looking at it. It passed tests in my case (I did the usual round).
It works here too. That's why I never noticed.
Yesterday I
On 07/05/2019 22:26, Richard Weinberger wrote:
On Thu, Apr 11, 2019 at 11:50 AM Bartosz Golaszewski wrote:
From: Bartosz Golaszewski
Setting a chip for an interrupt marks it as allocated. Since UM doesn't
support dynamic interrupt numbers (yet), it means we cannot simply
increase NR_IRQS
On Thu, Apr 11, 2019 at 11:50 AM Bartosz Golaszewski wrote:
>
> From: Bartosz Golaszewski
>
> Setting a chip for an interrupt marks it as allocated. Since UM doesn't
> support dynamic interrupt numbers (yet), it means we cannot simply
> increase NR_IRQS and then use the free irqs between
From: Bartosz Golaszewski
Setting a chip for an interrupt marks it as allocated. Since UM doesn't
support dynamic interrupt numbers (yet), it means we cannot simply
increase NR_IRQS and then use the free irqs between LAST_IRQ and NR_IRQS
with gpio-mockup or iio testing drivers as
From: Bartosz Golaszewski
Setting a chip for an interrupt marks it as allocated. Since UM doesn't
support dynamic interrupt numbers (yet), it means we cannot simply
increase NR_IRQS and then use the free irqs between LAST_IRQ and NR_IRQS
with gpio-mockup or iio testing drivers as
9 matches
Mail list logo
