Subject: Re: [net-next v3 3/7] mv88e6xxx: reject unsupported external timestamp flags

From: Richard Cochran <[email-masked]>
Date: Sat, 12 Oct 2019 16:27:19 -0700

On Sat, Oct 12, 2019 at 07:36:31PM +0000, Keller, Jacob E wrote:
> Right, so in practice, unless it supports both edges, it should reject setting both RISING and FALLING together.

Enforcing that now *could* break existing user space, but I wonder
whether any programs would actually be affected.

Maybe we can add a STRICT flag than requests strict checking.  If user
space uses the "2" ioctl, then we would add this flag before invoking
the driver callback.

Thanks,
Richard