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 1B12BC43217 for ; Tue, 8 Nov 2022 14:43:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234421AbiKHOnW (ORCPT ); Tue, 8 Nov 2022 09:43:22 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47766 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232367AbiKHOnV (ORCPT ); Tue, 8 Nov 2022 09:43:21 -0500 Received: from mail-qk1-f178.google.com (mail-qk1-f178.google.com [209.85.222.178]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2102631ECF; Tue, 8 Nov 2022 06:43:20 -0800 (PST) Received: by mail-qk1-f178.google.com with SMTP id p18so4626390qkg.2; Tue, 08 Nov 2022 06:43:20 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=chPq10Gzwk+MmB+dQBE8YARzKswl0L8S0c4cotUK9Yo=; b=Nel+RCouuBuJs1TaAED5Cvd/nfznpqnUTi9Q0+X++UdFTeQ4MNw88NfXMK0pdiBLVp xr4K+7kkKqYRk4HW5P2C7UsMk6UT9ghbd++Z0KEBUNJFPHGzJ3t1Whmuzz+oybC8xZQQ xURZD392gkNacpyQ3UPKy7LPBjh5/BRtiqEbdAGRoEWuiViwRRuw+Cm+elPpe5V0rvG/ hsUAC/lkUEcKXq9GgtvdSke5QkeKvzTVxPjutX5/MzFbrqWD7cKyWZynmc5oI4MiLiNN XOI/y1sJDeroHBMAOocVfr5t+RXxtTj73YRUz8PDlgKSMy+Qb93ohs0WFYBlSRA3GVGq Y7lA== X-Gm-Message-State: ACrzQf0yBEiLduDrjmQczD9clJEByYdLMt414dNPUvhaFomUL06dYzzr N55IUZIiIeP9qF3VU9aF3v4FAKoixSJiuwjHbzI= X-Google-Smtp-Source: AMsMyM61bIp/lkNqz9d4L2NL67oaG2AS8g2ED2d2BN7jytLEkidQhYJsMKVpa/kDJFQhN8K4Q8s3uCUrZF8Mm0Ykuqc= X-Received: by 2002:a05:620a:d89:b0:6cf:c98b:744c with SMTP id q9-20020a05620a0d8900b006cfc98b744cmr38559368qkl.443.1667918599300; Tue, 08 Nov 2022 06:43:19 -0800 (PST) MIME-Version: 1.0 References: <2276401.ElGaqSPkdT@kreacher> <8155359.T7Z3S40VBb@kreacher> In-Reply-To: From: "Rafael J. Wysocki" Date: Tue, 8 Nov 2022 15:43:08 +0100 Message-ID: Subject: Re: [PATCH v1 4/5] rtc: rtc-cmos: Rename ACPI-related functions To: Andy Shevchenko Cc: "Rafael J. Wysocki" , Alexandre Belloni , linux-rtc@vger.kernel.org, Linux ACPI , LKML , Linux PM , Zhang Rui , Alessandro Zummo Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-acpi@vger.kernel.org On Mon, Nov 7, 2022 at 10:22 PM Andy Shevchenko wrote: > > On Mon, Nov 07, 2022 at 09:01:50PM +0100, Rafael J. Wysocki wrote: > > From: Rafael J. Wysocki > > > > The names of rtc_wake_setup() and cmos_wake_setup() don't indicate > > that these functions are ACPI-related, which is the case, and the > > former doesn't really reflect the role of the function. > > > > Rename them to acpi_rtc_event_setup() and cmos_acpi_wake_setup(), > > respectively, to address this shortcoming. > > Hmm... I'm not sure I understand why in one case acpi is a prefix and > in the other is kinda mid-suffix? Because the former installs an ACPI RTC fixed event handler and the latter populates the cmos_rtc data structure in the ACPI case. Maybe it would be better to call the latter cmos_wake_setup_acpi().