On Wed, May 11, 2016 at 01:54:52PM -0700, Keith Packard wrote: > When this code was called from SIGIO, saving and restoring errno could > possibly have made sense in some strange environment. Now that this > will not be called from a signal handler, there is no reason to do that. > > Signed-off-by: Keith Packard <[email protected]>
Reviewed-by: Peter Hutterer <[email protected]> Cheers, Peter > --- > hw/xfree86/common/xf86Events.c | 3 --- > 1 file changed, 3 deletions(-) > > diff --git a/hw/xfree86/common/xf86Events.c b/hw/xfree86/common/xf86Events.c > index 81416ed..df8c7b6 100644 > --- a/hw/xfree86/common/xf86Events.c > +++ b/hw/xfree86/common/xf86Events.c > @@ -298,12 +298,9 @@ xf86Wakeup(void *blockData, int err, void *pReadmask) > static void > xf86ReadInput(int fd, int ready, void *closure) > { > - int errno_save = errno; > InputInfoPtr pInfo = closure; > > pInfo->read_input(pInfo); > - > - errno = errno_save; > } > > /* > -- > 2.8.0.rc3 > > _______________________________________________ > [email protected]: X.Org development > Archives: http://lists.x.org/archives/xorg-devel > Info: https://lists.x.org/mailman/listinfo/xorg-devel > _______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: https://lists.x.org/mailman/listinfo/xorg-devel
