From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 04A6CC43381 for ; Sat, 30 Mar 2019 20:06:27 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id BFF66218D0 for ; Sat, 30 Mar 2019 20:06:26 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=hansenpartnership.com header.i=@hansenpartnership.com header.b="W+DEUDA+" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730917AbfC3UG0 (ORCPT ); Sat, 30 Mar 2019 16:06:26 -0400 Received: from bedivere.hansenpartnership.com ([66.63.167.143]:53252 "EHLO bedivere.hansenpartnership.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730740AbfC3UG0 (ORCPT ); Sat, 30 Mar 2019 16:06:26 -0400 Received: from localhost (localhost [127.0.0.1]) by bedivere.hansenpartnership.com (Postfix) with ESMTP id 56F6F8EE051; Sat, 30 Mar 2019 13:06:25 -0700 (PDT) Received: from bedivere.hansenpartnership.com ([127.0.0.1]) by localhost (bedivere.hansenpartnership.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09osN0Ul1R7i; Sat, 30 Mar 2019 13:06:25 -0700 (PDT) Received: from [153.66.254.194] (unknown [50.35.68.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bedivere.hansenpartnership.com (Postfix) with ESMTPSA id 399208EE03B; Sat, 30 Mar 2019 13:06:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=hansenpartnership.com; s=20151216; t=1553976384; bh=eAEN4EjDoewYfyGZk2PjmvkqR/BN7klHc2JOWBt9Ru0=; h=Subject:From:To:Cc:Date:In-Reply-To:References:From; b=W+DEUDA+0FNmFDlHlf3MWKRG/SonddV3SIGLR/eTT5hO0faPrIR7Q+xTIxtbuxPKT /C0ICAEAUKiMlhPp3CSBR/yDlUexHhsgPQfgoikfnLi3Y3TvZ6JoBusMzjxTeW48cA fioFZu6WnlW9NrQ8gJHHTEoOWj5umM7rVev8Ajuk= Message-ID: <1553976383.2893.15.camel@HansenPartnership.com> Subject: Re: FAILED: patch "[PATCH] USB: gadget: f_hid: fix deadlock in f_hidg_write()" failed to apply to 4.9-stable tree From: James Bottomley To: gregkh@linuxfoundation.org, rgerganov@vmware.com, felipe.balbi@linux.intel.com Cc: stable@vger.kernel.org Date: Sat, 30 Mar 2019 13:06:23 -0700 In-Reply-To: <1553975841150122@kroah.com> References: <1553975841150122@kroah.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.26.6 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Sat, 2019-03-30 at 20:57 +0100, gregkh@linuxfoundation.org wrote: > The patch below does not apply to the 4.9-stable tree. > If someone wants it applied there, or to any other stable or longterm > tree, then please email the backport, including the original git > commit id to . [...] > Cc: stable@vger.kernel.org # 4.11+ > Fixes: 749494b6bdbb ("usb: gadget: f_hid: fix: Move IN request > allocation to set_alt()") The cc: stable specifies 4.11+ because the commit it fixes went in in the 4.11 merge window. Is there something incorrect with the tagging that makes you think it should apply to 4.9? James