Received: by 2002:a05:6358:53a8:b0:117:f937:c515 with SMTP id z40csp90298rwe; Thu, 13 Apr 2023 22:54:07 -0700 (PDT) X-Google-Smtp-Source: AKy350aa0axASrNSn0sObJgc9lGxU3sBpcUMrTfUeyRMKQ9BNHiqt9hvSufsrzSmOVtrylLB1BPx X-Received: by 2002:a05:6a00:892:b0:627:6328:79f1 with SMTP id q18-20020a056a00089200b00627632879f1mr6451270pfj.34.1681451647601; Thu, 13 Apr 2023 22:54:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1681451647; cv=none; d=google.com; s=arc-20160816; b=plag1oOUBBt+VlKnT6ncej+6QlWRB1vtovo62JE7FE0NoiFFKPTSaS2K1V6H6HrFq3 jfDLY9JX+/ftllYPCA+abBEKIaj02Cir+3f9P5UnjzQJmc0aMH5WT9v9NgSMVexDgt19 5PLKfOI29+FBQZoWxWEugVjvEGZb86UixbCP2qgVf6Wali3T+avaAheZ2a8RHs0kLgmc p3BtdfH8v0I14mNZElFSsJ0HKuLp+7WnW25d13IP9bAKSQOMuVq/AY7Mwnr79HsxIF/x S8ZIzDpptzUCNjQv/vPLw4kA3BB+BQCtasMkmjOPfeh/5xjBYOY+RhQeNscmmVKM5okN VCSQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=4pHgsQWQwI71hZgnX5AYNpS5K/ti9aj57p0hS17Mteo=; b=cLLOgrA46hpIbsbwXiDEqlVuv2IQUsBUChlQDOjk0x3wVjZ8JKWZwcOb1Iq6XP77MA mlzbCRNVAZK1mJ1u8Jh1cBFZ5AS7xVyD1wxt1DxhA7SvS2Ut8GrBQ95vipBFchSi4ZAu 46zgWpn5qONBpiPpRsxSZfTwyWSBD2nnctyGcUocmcBmu6iOopPXBx3YPlB7h8jubq7N 9/W8cQ9rsVFD2Gq2hfijyL/Cubk9QDrgDjoihb2BqUOkVElhUtVkCrgOG/UKnl/vXLaq 9ALzq86qyUxRfpBbzjhRWS10NZUc24lq7fx0OPeft31pLTD4w+37ZkggiY8NFChXPl9+ cbcw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id a21-20020a63e855000000b004fb33a76e2csi3835395pgk.834.2023.04.13.22.53.56; Thu, 13 Apr 2023 22:54:07 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229773AbjDNFra (ORCPT + 99 others); Fri, 14 Apr 2023 01:47:30 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33180 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229534AbjDNFr3 (ORCPT ); Fri, 14 Apr 2023 01:47:29 -0400 Received: from muru.com (muru.com [72.249.23.125]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 7EBC52738; Thu, 13 Apr 2023 22:47:28 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by muru.com (Postfix) with ESMTPS id 9C70A80F0; Fri, 14 Apr 2023 05:47:27 +0000 (UTC) Date: Fri, 14 Apr 2023 08:47:26 +0300 From: Tony Lindgren To: Andy Shevchenko Cc: Greg Kroah-Hartman , Jiri Slaby , Ilpo =?utf-8?B?SsOkcnZpbmVu?= , Johan Hovold , Sebastian Andrzej Siewior , Vignesh Raghavendra , linux-omap@vger.kernel.org, linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] serial: 8250: Clear port->pm on port specific driver unbind Message-ID: <20230414054726.GE36234@atomide.com> References: <20230413070342.36155-1-tony@atomide.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_NONE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Andy Shevchenko [230413 16:06]: > On Thu, Apr 13, 2023 at 10:03:41AM +0300, Tony Lindgren wrote: > > Let's fix the issue by clearing port->pm in serial8250_unregister_port(). > > Sounds to me like a fix that needs a Fixes tag. Maybe commit c161afe9759d ("8250: allow platforms to override PM hook."). That's a bit unclear though as the hardware specific functions were available at that point as they were passed in platform data. This can be seen with git blame c161afe9759d drivers/serial/8250.c. To me it seems the port->pm became potentially invalid if a serial port device driver started implementing PM runtime? Maybe just tagging it with Cc: stable is better if no obvious Fixes tag can be figured out. > Code wise LGTM, > Reviewed-by: Andy Shevchenko OK thanks, Tony