From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752212AbbJLS50 (ORCPT ); Mon, 12 Oct 2015 14:57:26 -0400 Received: from mail-pa0-f43.google.com ([209.85.220.43]:33369 "EHLO mail-pa0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751657AbbJLS5Y (ORCPT ); Mon, 12 Oct 2015 14:57:24 -0400 Date: Mon, 12 Oct 2015 11:57:23 -0700 From: Dustin Byford To: "Rafael J. Wysocki" Cc: Mika Westerberg , Wolfram Sang , linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org, Andriy Shevchenko , Lee Jones Subject: Re: [PATCH 1/2] i2c: scan entire ACPI namespace for I2C connections Message-ID: <20151012185723.GA11643@cumulusnetworks.com> References: <1439580693-5538-1-git-send-email-dustin@cumulusnetworks.com> <1444437707-19027-1-git-send-email-dustin@cumulusnetworks.com> <1444437707-19027-2-git-send-email-dustin@cumulusnetworks.com> <7153761.vXTXx4WAKT@vostro.rjw.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7153761.vXTXx4WAKT@vostro.rjw.lan> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon Oct 12 21:01, Rafael J. Wysocki wrote: > On Friday, October 09, 2015 05:41:46 PM Dustin Byford wrote: > > An I2cSerialBus connection resource descriptor may indicate a > > ResourceSource (a string uniquely identifying the I2C bus controller) > > anywhere in the ACPI namespace. However, when enumerating connections to a > > I2C bus controller, i2c-core.c:acpi_i2c_register_devices() as only > > searching devices that are descendants of the bus controller. > > > > This change corrects acpi_i2c_register_devices() to walk the entire ACPI > > namespace searching for I2C connections. > > > > Suggested-by: Mika Westerberg > > Signed-off-by: Dustin Byford > > This one has already been submitted by Andy and I've ACKed it. Sorry, I missed that before I sent the patch. > I'm not sure what to do here, though. > > I guess I can apply this one and put it into a branch for others to pull from. > > Thoughts? I'd be OK if you just drop this patch and I won't include it in my next revision. --Dustin