From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-input-owner@kernel.org>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
	aws-us-west-2-korg-lkml-1.web.codeaurora.org
Received: from vger.kernel.org (vger.kernel.org [23.128.96.18])
	by smtp.lore.kernel.org (Postfix) with ESMTP id C315BC00140
	for <linux-input@archiver.kernel.org>; Thu, 18 Aug 2022 13:11:06 +0000 (UTC)
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S244250AbiHRNLG (ORCPT <rfc822;linux-input@archiver.kernel.org>);
        Thu, 18 Aug 2022 09:11:06 -0400
Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36376 "EHLO
        lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S244526AbiHRNLE (ORCPT
        <rfc822;linux-input@vger.kernel.org>);
        Thu, 18 Aug 2022 09:11:04 -0400
Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1])
        by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 80830B08B7
        for <linux-input@vger.kernel.org>; Thu, 18 Aug 2022 06:10:59 -0700 (PDT)
Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140])
        (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
        (No client certificate requested)
        by ams.source.kernel.org (Postfix) with ESMTPS id 1E139B81FC7
        for <linux-input@vger.kernel.org>; Thu, 18 Aug 2022 13:10:58 +0000 (UTC)
Received: by smtp.kernel.org (Postfix) with ESMTPSA id 682D7C433C1;
        Thu, 18 Aug 2022 13:10:56 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org;
        s=korg; t=1660828256;
        bh=mvtkMfCjDMNu5vyI7NOCU1VYdsVLKhImqb0n0zaE338=;
        h=Date:From:To:Cc:Subject:References:In-Reply-To:From;
        b=O8DNmTeNY5xT8hnWF4vaDaIQK0mRe5HGse+P3wr/Ex9nWz8rUQYFF6qQ8EsMBOMjn
         cS21PVrIX+bjZPMHlMCQwQcJ6KzpxmPaq4sanjBrWagPGf8HbQH4JwlspbVpD2Otsv
         MIPOBCtpNhGzRVeTVOIuU70u7mwsrxVjqj/xBzqM=
Date:   Thu, 18 Aug 2022 15:10:53 +0200
From:   Greg KH <gregkh@linuxfoundation.org>
To:     Pavel Rojtberg <rojtberg@gmail.com>
Cc:     linux-input@vger.kernel.org, dmitry.torokhov@gmail.com,
        Cameron Gutman <aicommander@gmail.com>
Subject: Re: [PATCH 2/4] Input: xpad - fix wireless 360 controller breaking
 after suspend
Message-ID: <Yv46XUD1/Kx9cGcy@kroah.com>
References: <20220818130021.487410-1-rojtberg@gmail.com>
 <20220818130021.487410-3-rojtberg@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20220818130021.487410-3-rojtberg@gmail.com>
Precedence: bulk
List-ID: <linux-input.vger.kernel.org>
X-Mailing-List: linux-input@vger.kernel.org

On Thu, Aug 18, 2022 at 03:00:19PM +0200, Pavel Rojtberg wrote:
> From: Cameron Gutman <aicommander@gmail.com>
> 
> Suspending and resuming the system can sometimes cause the out
> URB to get hung after a reset_resume. This causes LED setting
> and force feedback to break on resume. To avoid this, just drop
> the reset_resume callback so the USB core rebinds xpad to the
> wireless pads on resume if a reset happened.
> 
> A nice side effect of this change is the LED ring on wireless
> controllers is now set correctly on system resume.
> 
> Signed-off-by: Cameron Gutman <aicommander@gmail.com>
> Signed-off-by: Pavel Rojtberg <rojtberg@gmail.com>
> ---
>  drivers/input/joystick/xpad.c | 1 -
>  1 file changed, 1 deletion(-)

What commit id does this fix?  Should it go to stable kernels?

thanks,

greg k-h