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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 40AC9C433FE for ; Sat, 22 Jan 2022 00:04:59 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230012AbiAVAE6 (ORCPT ); Fri, 21 Jan 2022 19:04:58 -0500 Received: from alexa-out-sd-01.qualcomm.com ([199.106.114.38]:4706 "EHLO alexa-out-sd-01.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229517AbiAVAE5 (ORCPT ); Fri, 21 Jan 2022 19:04:57 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quicinc.com; i=@quicinc.com; q=dns/txt; s=qcdkim; t=1642809897; x=1674345897; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=M4xJpCeE5aKhJ84AV5MByeatBIkGIFocgtR0PeuZbQA=; b=hkjdMJiF8jjFsvgrR4mAKbXSqynY/x6TiTJyQosEPgJOFqkxN7HqDtvT dexoILSoPWpD22NjM8qNeMSWkjtItubg+7elTfHKT3spvVlc/tm7+YVQ0 MFoNqNlKJn2G8OwZbf9DHXcSYb1WYPdPtK0JXsK0fg29WwJB0/ivxIEgg I=; Received: from unknown (HELO ironmsg05-sd.qualcomm.com) ([10.53.140.145]) by alexa-out-sd-01.qualcomm.com with ESMTP; 21 Jan 2022 16:04:57 -0800 X-QCInternal: smtphost Received: from nasanex01c.na.qualcomm.com ([10.47.97.222]) by ironmsg05-sd.qualcomm.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Jan 2022 16:04:57 -0800 Received: from nalasex01a.na.qualcomm.com (10.47.209.196) by nasanex01c.na.qualcomm.com (10.47.97.222) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.922.19; Fri, 21 Jan 2022 16:04:56 -0800 Received: from [10.110.112.109] (10.80.80.8) by nalasex01a.na.qualcomm.com (10.47.209.196) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.922.19; Fri, 21 Jan 2022 16:04:56 -0800 Message-ID: <11a2047f-86b8-1bea-ff99-d708429327fd@quicinc.com> Date: Fri, 21 Jan 2022 16:04:55 -0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: [PATCH 0/3] Add support for pm8941-pwrkey.c Content-Language: en-US To: Stephen Boyd , CC: , , , , , References: <20220120204132.17875-1-quic_amelende@quicinc.com> From: Anjelique Melendez In-Reply-To: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.80.80.8] X-ClientProxiedBy: nasanex01a.na.qualcomm.com (10.52.223.231) To nalasex01a.na.qualcomm.com (10.47.209.196) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 1/20/2022 7:51 PM, Stephen Boyd wrote: > "Add support" in the subject sounds like it is new. Maybe "extend > pm8941-pwrkey driver" would be more appropriate. Will update subject in upcoming version. > Quoting Anjelique Melendez (2022-01-20 12:41:30) >> This change series includes support and fixes in pm8941-pwrkey.c. >> Change details and description can be found in each patch. Thanks! >> >> David Collins (3): >> input: misc: pm8941-pwrkey: simulate missed key press events >> input: misc: pm8941-pwrkey: add software key press debouncing support >> input: misc: pm8941-pwrkey: avoid potential null pointer dereference