From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <SRS0=5tOS=ZP=vger.kernel.org=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
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED,
	DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,
	SPF_PASS,USER_AGENT_SANE_1 autolearn=no 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 3B3C3C432C3
	for <stable@archiver.kernel.org>; Sat, 23 Nov 2019 09:27:06 +0000 (UTC)
Received: from vger.kernel.org (vger.kernel.org [209.132.180.67])
	by mail.kernel.org (Postfix) with ESMTP id 0D1592071B
	for <stable@archiver.kernel.org>; Sat, 23 Nov 2019 09:27:05 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org;
	s=default; t=1574501226;
	bh=Mnf2M58/rhc8aWQSqhoykSytTknTxW16bUn0An3Nr00=;
	h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From;
	b=EUi81fbFA4RumBMIvFCEfM3HPZLSz7DhYwFR0oeHr5SrvLVPD/KqCzOUbkKC2j7a+
	 36HO/zJvvLpcW93cTlmLyzlDmz/Kq9b/WuxYJLbn3oEWcJQN//rvLAkttoTz+hvrHZ
	 +Sbvs96Kl4jD+r/5CUVg4Hgnps3aJxgGKX6Ec8lY=
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1726304AbfKWJ1F (ORCPT <rfc822;stable@archiver.kernel.org>);
        Sat, 23 Nov 2019 04:27:05 -0500
Received: from mail.kernel.org ([198.145.29.99]:40660 "EHLO mail.kernel.org"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1726141AbfKWJ1F (ORCPT <rfc822;stable@vger.kernel.org>);
        Sat, 23 Nov 2019 04:27:05 -0500
Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107])
        (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
        (No client certificate requested)
        by mail.kernel.org (Postfix) with ESMTPSA id C817D20719;
        Sat, 23 Nov 2019 09:27:03 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org;
        s=default; t=1574501224;
        bh=Mnf2M58/rhc8aWQSqhoykSytTknTxW16bUn0An3Nr00=;
        h=Date:From:To:Cc:Subject:References:In-Reply-To:From;
        b=NBlkZeAgegxDeezSpfAAicIqkFD2CqFhmm57mNmqlswt9sHBEWvCfaNOBwD5opLOH
         yhEkOCizO72GwuJfMTHzpKv7lPvuNV2gMb+xLJXoCyEtDSiBePO5tcmlunEErmdqvJ
         dxDPai3CI92uCQZrxDgyw/z6PXcf1Kv/HIRUWyxw=
Date:   Sat, 23 Nov 2019 10:27:01 +0100
From:   Greg KH <gregkh@linuxfoundation.org>
To:     Bob Funk <bobfunk11@gmail.com>
Cc:     sashal@kernel.org, stable@vger.kernel.org
Subject: Re: Bug Report - Kernel Branch 4.4.y - asus-wmi.c
Message-ID: <20191123092701.GA2129125@kroah.com>
References: <33bfa93a-3853-85f5-47f9-8a69ed9c656e@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <33bfa93a-3853-85f5-47f9-8a69ed9c656e@gmail.com>
User-Agent: Mutt/1.12.2 (2019-09-21)
Sender: stable-owner@vger.kernel.org
Precedence: bulk
List-ID: <stable.vger.kernel.org>
X-Mailing-List: stable@vger.kernel.org

On Fri, Nov 22, 2019 at 08:33:46PM -0600, Bob Funk wrote:
> Hello,
> 
> I am contacting the stable branch maintainers with a bug report concerning
> the asus-wmi kernel driver in the 4.4 kernel branch. I had initially
> contacted
> maintainers for the specific driver and received a response stating that I
> should contact the stable branch maintainers about the issue instead. Their
> opinion was that the patch in question should be reverted rather than
> debugged. I will append my initial report here and let you decide what to do
> with the bug.

Any reason you can not just use 5.3 or newer for this hardware?  Why are
you stuck on 4.4?

thanks,

greg k-h