From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 3CB32145A18; Mon, 20 Jan 2025 07:11:41 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1737357102; cv=none; b=gFuuBkg/RHoZ/YAn5wcXgBqASlnrpep0sUNpXj2K5edT7wtI1eHu28XELzXg1r/1caDEN7YlMRQFfTLhib5wWUKE5trsszteE0niYn8IS7gjuu8xH0sc6LayFX8dQXQ5diamNTOFmEGMyMUySXhIkT2DzUkD7b5TFBL/szc8K4s= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1737357102; c=relaxed/simple; bh=UsYUJ1dfu3HtvbDCIPPjsGBIQ9q1bsv5BjYbYRwgLhY=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=ITxJ/73O1n5sPuPMlyKUxDyh3ImRB+G0mF7s3kxlW7QPv+ac8pE6Z5i1M27tTG/0dtiOyAwq42v1kQDBrul1psensETsKmP1bLyU/x+UDsRqxCdGxqvCLuRkL1B9s1eRTiSQMEl3JRcMM6aBJ9nwdXqbq0IxRxoXoPmeWUJinuQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=kcHCvlJn; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="kcHCvlJn" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5FCBDC4CEDD; Mon, 20 Jan 2025 07:11:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1737357101; bh=UsYUJ1dfu3HtvbDCIPPjsGBIQ9q1bsv5BjYbYRwgLhY=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=kcHCvlJnmp98NjrBfT917l6/uHCgT+k9MAAKjubdYZ0IvLCvez8gh5Aa/vAthn04s rhnn/GN+1OZaDDeGcUQbQp5KPkZBEeURwciye3uHChkURT2Kk0wnRLzfhJ6xG5eBBk Eq9/i1KimsJKvDJbVA8qb+533tJV716ZeTsNqua7k+Qy6WogVsInTcy18j/ufut4qO jT3eOAJEnFcqCQt/Wn1LK0E+jn/BnJMPgee3YetSeaymOIlOiUTl9fNBF6Js2x68Fx EJhDSTBUVYvZdapQBDjgeTXgy3+lvFpVzO0qpplWNfclEywuKmpGaqccHcF0yGoAxD TmgkhhVhgE5lw== Date: Mon, 20 Jan 2025 07:11:35 +0000 From: Tzung-Bi Shih To: Ahmad Fatoum Cc: Andrew Morton , Daniel Lezcano , Fabio Estevam , "Rafael J. Wysocki" , Zhang Rui , Lukasz Luba , Jonathan Corbet , Serge Hallyn , Liam Girdwood , Mark Brown , Matti Vaittinen , Benson Leung , Guenter Roeck , Rob Herring , Krzysztof Kozlowski , Conor Dooley , linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, linux-doc@vger.kernel.org, linux-security-module@vger.kernel.org, chrome-platform@lists.linux.dev, devicetree@vger.kernel.org, kernel@pengutronix.de Subject: Re: [PATCH v2 05/12] reboot: rename now misleading __hw_protection_shutdown symbols Message-ID: References: <20250113-hw_protection-reboot-v2-0-161d3fc734f0@pengutronix.de> <20250113-hw_protection-reboot-v2-5-161d3fc734f0@pengutronix.de> Precedence: bulk X-Mailing-List: linux-security-module@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20250113-hw_protection-reboot-v2-5-161d3fc734f0@pengutronix.de> On Mon, Jan 13, 2025 at 05:25:30PM +0100, Ahmad Fatoum wrote: > The __hw_protection_shutdown function name has become misleading > since it can cause either a shutdown (poweroff) or a reboot > depending on its argument. > > To avoid further confusion, let's rename it, so it doesn't suggest > that a poweroff is all it can do. > > Signed-off-by: Ahmad Fatoum Reviewed-by: Tzung-Bi Shih