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=-5.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=unavailable 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 119CFC3A5A6 for ; Mon, 23 Sep 2019 13:30:29 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id D2BB520B7C for ; Mon, 23 Sep 2019 13:30:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1569245428; bh=CA3jF6Gt7vTntOiNm7Ka9iK9XTY7AzxUYxpyJSRtT+o=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=U3unQ3YCy0WCO99Y0MaS47NTOlsyTFlSjIzdthc1zGqfPU/7VehBqlZCFfej0ZdLV q4kDK7Yq5pw8cS7fChIef4bOcwevrmqoR3uPH7PWhZNdotKkwNY+EIuWkIpiA/yKNB ISztqF3/XlfB9LHJJ90IWsgqn7UwQZtqA4x3EvuU= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2407776AbfIWNa2 (ORCPT ); Mon, 23 Sep 2019 09:30:28 -0400 Received: from mail.kernel.org ([198.145.29.99]:56812 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2404581AbfIWNa2 (ORCPT ); Mon, 23 Sep 2019 09:30:28 -0400 Received: from localhost (c-73-47-72-35.hsd1.nh.comcast.net [73.47.72.35]) (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 DEF5A20867; Mon, 23 Sep 2019 13:30:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1569245427; bh=CA3jF6Gt7vTntOiNm7Ka9iK9XTY7AzxUYxpyJSRtT+o=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=vs1xNEWZ/cH9GY0nruq1EHVFCmL/BQMrp8GEO7tRzWK4V9PTUO0pDnlnRPn0iPf+z unyrvy+QABye++Z/AdZ7j7DyFrSNT5kc31Aiw3nrmdnv82QGRlg1hCVSRvZFDiEOth /3IHlWp3MAKcOGTobl6cbgCyoqhjSf7HUCglg544= Date: Mon, 23 Sep 2019 09:30:25 -0400 From: Sasha Levin To: Takashi Iwai Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org Subject: Re: [PATCH AUTOSEL 5.2 072/185] ALSA: hda: Add codec on bus address table lately Message-ID: <20190923133025.GE8171@sasha-vm> References: <20190922184924.32534-1-sashal@kernel.org> <20190922184924.32534-72-sashal@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Sep 22, 2019 at 09:06:12PM +0200, Takashi Iwai wrote: >On Sun, 22 Sep 2019 20:47:30 +0200, >Sasha Levin wrote: >> >> From: Takashi Iwai >> >> [ Upstream commit ee5f85d9290fe25d460bd320b7fe073075d72d33 ] >> >> The call of snd_hdac_bus_add_device() is needed only for registering >> the codec onto the bus caddr_tbl[] that is referred essentially only >> in the unsol event handler. That is, the reason of this call and the >> release by the counter-part function snd_hdac_bus_remove_device() is >> just to assure that the unsol event gets notified to the codec. >> >> But the current implementation of the unsol notification wouldn't work >> properly when the codec is still in a premature init state. So this >> patch tries to work around it by delaying the caddr_tbl[] registration >> at the point of snd_hdac_device_register(). >> >> Also, the order of snd_hdac_bus_remove_device() and device_del() calls >> are shuffled to make sure that the unsol event is masked before >> deleting the device. >> >> BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=204565 >> Signed-off-by: Takashi Iwai >> Signed-off-by: Sasha Levin > >The upstream commit was reverted later by 246bb4aaa4f4, which has even >Fixes tag pointing this. So please drop this. I'll drop it, thank you. >BTW, this is the second time AUTOSEL overlooked the existing revert. >I'm afraid something is missing in the check. Usually it's the case that I check for fixes/reverts once I compile the series, and again right before I queue it up to a stable tree. In between fixes and reverts tend to sneak in just like in this case. In general, I also check the -rcs for fixes and reverts during their review window, so while sometimes we send out mails with patches that have a fix or revert upstream, they rarely make it into a released stable kernel. -- Thanks, Sasha