Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936462Ab3DHOaZ (ORCPT ); Mon, 8 Apr 2013 10:30:25 -0400 Received: from mga09.intel.com ([134.134.136.24]:31762 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S936441Ab3DHOaV (ORCPT ); Mon, 8 Apr 2013 10:30:21 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.87,432,1363158000"; d="scan'208";a="314727387" Date: Mon, 8 Apr 2013 16:30:08 +0200 From: Samuel Ortiz To: Mark Brown Cc: linux-kernel@vger.kernel.org, patches@opensource.wolfsonmicro.com, Grant Likely , devicetree-discuss@lists.ozlabs.org Subject: Re: [PATCH] mfd: Add device tree bindings for Arizona class devices Message-ID: <20130408143008.GA21256@zurbaran> References: <1364938728-7732-1-git-send-email-broonie@opensource.wolfsonmicro.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1364938728-7732-1-git-send-email-broonie@opensource.wolfsonmicro.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1094 Lines: 27 Hi Mark, On Tue, Apr 02, 2013 at 10:38:48PM +0100, Mark Brown wrote: > Signed-off-by: Mark Brown > --- > Documentation/devicetree/bindings/mfd/arizona.txt | 62 ++++++++++++++++++++ > drivers/mfd/arizona-core.c | 64 +++++++++++++++++++++ > drivers/mfd/arizona-i2c.c | 10 +++- > drivers/mfd/arizona-spi.c | 10 +++- > drivers/mfd/arizona.h | 12 ++++ > 5 files changed, 154 insertions(+), 4 deletions(-) > create mode 100644 Documentation/devicetree/bindings/mfd/arizona.txt This is the one that caused the build failure around missing arizona_of_get_core_pdata() with !CONFIG_OF, so I'm leaving this one out for now. Cheers, Samuel. -- Intel Open Source Technology Centre http://oss.intel.com/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/