[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y/5QX1gYsGinrPNF@kroah.com>
Date: Tue, 28 Feb 2023 20:05:03 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: "Limonciello, Mario" <Mario.Limonciello@....com>
Cc: Oliver Neukum <oneukum@...e.com>,
Michael Wu <michael@...winnertech.com>,
"jikos@...nel.org" <jikos@...nel.org>,
"benjamin.tissoires@...hat.com" <benjamin.tissoires@...hat.com>,
"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
"linux-input@...r.kernel.org" <linux-input@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Gong, Richard" <Richard.Gong@....com>
Subject: Re: [PATCH] HID: usbhid: enable remote wakeup for mice
On Tue, Feb 28, 2023 at 06:50:18PM +0000, Limonciello, Mario wrote:
> I still keep getting inquiries about this where teams that work on the same
> hardware for Windows and Linux complain about this difference during
> their testing.
>
> I keep educating them to change it in sysfs (or to use a udev rule), but
> you have to question if you keep getting something asked about policy
> over and over if it's actually the right policy.
Why not complain to the Windows team to get them to change their policy
back as they are the ones that changed it over time and are not
backwards-compatible with older systems?
:)
thanks,
greg k-h
Powered by blists - more mailing lists