From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mika Westerberg Subject: Re: [RFC PATCH] i2c: acpi: put device when verifying client fails Date: Fri, 13 Mar 2020 13:29:32 +0200 Message-ID: <20200313112932.GA2540@lahna.fi.intel.com> References: <20200312133244.9564-1-wsa@the-dreams.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20200312133244.9564-1-wsa@the-dreams.de> Sender: linux-acpi-owner@vger.kernel.org To: Wolfram Sang Cc: linux-i2c@vger.kernel.org, linux-acpi@vger.kernel.org, linux-renesas-soc@vger.kernel.org, Andy Shevchenko , Jarkko Nikula , Wolfram Sang , Geert Uytterhoeven List-Id: linux-i2c@vger.kernel.org On Thu, Mar 12, 2020 at 02:32:44PM +0100, Wolfram Sang wrote: > From: Wolfram Sang > > i2c_verify_client() can fail, so we need to put the device when that > happens. > > Fixes: 525e6fabeae2 ("i2c / ACPI: add support for ACPI reconfigure notifications") > Reported-by: Geert Uytterhoeven > Signed-off-by: Wolfram Sang > --- > > RFC because I don't know if it can be that the returned dev is not an > i2c_client. Yet, since it can happen theoretically, I think we should > have the checks. I agree, Acked-by: Mika Westerberg