Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751840AbdITIeg (ORCPT <rfc822;w@1wt.eu>);
        Wed, 20 Sep 2017 04:34:36 -0400
Received: from mga02.intel.com ([134.134.136.20]:17932 "EHLO mga02.intel.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1751640AbdITIee (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 20 Sep 2017 04:34:34 -0400
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.42,420,1500966000"; 
   d="scan'208";a="137419788"
Date: Wed, 20 Sep 2017 11:34:29 +0300
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: john.hubbard@gmail.com, Sakari Ailus <sakari.ailus@linux.intel.com>,
        LKML <linux-kernel@vger.kernel.org>, Rob Herring <robh@kernel.org>,
        "Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
        John Hubbard <jhubbard@nvidia.com>
Subject: Re: [PATCH 1/1] acpi: unbreak ACPI_HANDLE(), encapsulate
 fwnode_operations
Message-ID: <20170920083429.GU4630@lahna.fi.intel.com>
References: <20170916003527.3081-1-jhubbard@nvidia.com>
 <20170916003527.3081-2-jhubbard@nvidia.com>
 <20170919074400.GG4630@lahna.fi.intel.com>
 <1712250.n7upXYL8Lq@aspire.rjw.lan>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1712250.n7upXYL8Lq@aspire.rjw.lan>
Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo
User-Agent: Mutt/1.8.3 (2017-05-23)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 245
Lines: 5

On Tue, Sep 19, 2017 at 10:39:36PM +0200, Rafael J. Wysocki wrote:
> Do we really ever pass anything other than struct acpi_device to
> ACPI_COMPANION_SET() as the second arg?

No, and we should not accept anything else than acpi_device either.