[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <IA1PR11MB609838020E63E04EF338C57EF4CB2@IA1PR11MB6098.namprd11.prod.outlook.com>
Date: Wed, 5 Mar 2025 08:45:23 +0000
From: "Xu, Even" <even.xu@...el.com>
To: Jiri Kosina <jikos@...nel.org>
CC: "bentiss@...nel.org" <bentiss@...nel.org>,
"srinivas.pandruvada@...ux.intel.com" <srinivas.pandruvada@...ux.intel.com>,
"mpearson-lenovo@...ebb.ca" <mpearson-lenovo@...ebb.ca>,
"linux-input@...r.kernel.org" <linux-input@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH RESEND v1] HID: Intel-thc-hid: Intel-quickspi: Correct
device state after S4
Thank you very much, Jiri!
Best Regards,
Even Xu
> -----Original Message-----
> From: Jiri Kosina <jikos@...nel.org>
> Sent: Wednesday, March 5, 2025 4:44 PM
> To: Xu, Even <even.xu@...el.com>
> Cc: bentiss@...nel.org; srinivas.pandruvada@...ux.intel.com; mpearson-
> lenovo@...ebb.ca; linux-input@...r.kernel.org; linux-kernel@...r.kernel.org
> Subject: RE: [PATCH RESEND v1] HID: Intel-thc-hid: Intel-quickspi: Correct device
> state after S4
>
> On Wed, 5 Mar 2025, Xu, Even wrote:
>
> > I didn't realize v1 patch already got applied, just sent out v2 patch
> > this morning. If so, could you just pick " [PATCH v2 1/2] HID:
> > Intel-thc-hid: Intel-quickspi: Correct device state names gramatically"
> > from v2 patch set for the naming fix? Those two patches have no
> > confliction/dependence.
>
> 2/2 now in hid.git#for-6.15/intel-thc. Thanks,
>
> --
> Jiri Kosina
> SUSE Labs
Powered by blists - more mailing lists