From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stable-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 84D88C433FE
	for <stable@archiver.kernel.org>; Wed, 26 Oct 2022 16:21:32 +0000 (UTC)
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S229995AbiJZQVb (ORCPT <rfc822;stable@archiver.kernel.org>);
        Wed, 26 Oct 2022 12:21:31 -0400
Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56778 "EHLO
        lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S229949AbiJZQVa (ORCPT
        <rfc822;stable@vger.kernel.org>); Wed, 26 Oct 2022 12:21:30 -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 2CDF25B791
        for <stable@vger.kernel.org>; Wed, 26 Oct 2022 09:21:30 -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 DB274B822F3
        for <stable@vger.kernel.org>; Wed, 26 Oct 2022 16:21:28 +0000 (UTC)
Received: by smtp.kernel.org (Postfix) with ESMTPSA id 3E033C433C1;
        Wed, 26 Oct 2022 16:21:27 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org;
        s=korg; t=1666801287;
        bh=qFYxcI2tc9Mz0XQHwpnJvE8H7mHHpqxnXBy65B8UFgs=;
        h=Date:From:To:Cc:Subject:References:In-Reply-To:From;
        b=tVBXfJFC5hfFtByHPGxXPOJWWrhPhbicQeNvSiJ/T41LMH0ZYMwwRxwz54Haa5pvB
         lg83xuLX5ec1tL1ZGlYNQu2phBXfCFjoN8/20JCZ5XcLuMYcU6F6HsPyfDHX4wMdrv
         6xLJU9H3UQeb5vop87Em8C0Y1ANzGcpWreIWJg84=
Date:   Wed, 26 Oct 2022 18:21:24 +0200
From:   Greg KH <gregkh@linuxfoundation.org>
To:     Alan Stern <stern@rowland.harvard.edu>
Cc:     linhaoguo86@gmail.com, mchehab@kernel.org, sean@mess.org,
        stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] media: mceusb: Use new
 usb_control_msg_*() routines" failed to apply to 6.0-stable tree
Message-ID: <Y1lehL94Q8p4Dpkn@kroah.com>
References: <166679706424177@kroah.com>
 <Y1lTk7Gn0XGdLfa7@rowland.harvard.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Y1lTk7Gn0XGdLfa7@rowland.harvard.edu>
Precedence: bulk
List-ID: <stable.vger.kernel.org>
X-Mailing-List: stable@vger.kernel.org

On Wed, Oct 26, 2022 at 11:34:43AM -0400, Alan Stern wrote:
> On Wed, Oct 26, 2022 at 05:11:04PM +0200, gregkh@linuxfoundation.org wrote:
> > 
> > The patch below does not apply to the 6.0-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 <stable@vger.kernel.org>.
> > 
> > Possible dependencies:
> > 
> > 41fd1cb61514 ("media: mceusb: Use new usb_control_msg_*() routines")
> 
> Greg:
> 
> I can submit a patch for the -stable trees that fixes the problem 
> reported by syzbot without converting the mceusb driver to use the new 
> usb_control_msg_*() routines.  Would that be okay?  Or do you prefer 
> simply not to include this patch (which merely fixes a warning) in the 
> stable kernels?

If it's just a warning, no need to really worry about it.  But note that
the usb_control_msg_*() functions are in 5.10.y and newer kernels, so
maybe just do this using the real functions for 5.15 and 6.0?

thanks,

greg k-h