* Liu Ping Fan <kernelf...@gmail.com> wrote:
> When programming ioapic pinX more than once, current code
> does not check whether the later attr (trigger&polarity) is the
> same as the former or not. This causes a broken semantic.
>
> Fix it by reporting -EBUSY, when attr is different.
Was this observed in real life somehow, and if yes, what is
the before/after behavior?
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
