From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751060AbdKTExD (ORCPT ); Sun, 19 Nov 2017 23:53:03 -0500 Received: from mail-lf0-f47.google.com ([209.85.215.47]:40538 "EHLO mail-lf0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750764AbdKTExB (ORCPT ); Sun, 19 Nov 2017 23:53:01 -0500 X-Google-Smtp-Source: AGs4zMa7HVCMZz8UknprI7C+2bS+xPIlHZE/jzgJAV8KEd/JuJRxpwcoLqR0hc1xsK7VzCm2ZK21IsLzHi0RMUoJ55Q= MIME-Version: 1.0 In-Reply-To: <20171119160318.41d7e85a@archlinux> References: <20171031021203.18248-1-joel@jms.id.au> <20171102144932.00001e17@huawei.com> <20171119160318.41d7e85a@archlinux> From: Joel Stanley Date: Mon, 20 Nov 2017 15:22:38 +1030 X-Google-Sender-Auth: _UY9UExxAFGdmF4KBx0mQ7II9fU Message-ID: Subject: Re: [PATCH v2] iio: adc: aspeed: Deassert reset in probe To: Jonathan Cameron Cc: Jonathan Cameron , Philipp Zabel , Rick Altherr , Rob Herring , Hartmut Knaack , Lars-Peter Clausen , Peter Meerwald-Stadler , linux-iio@vger.kernel.org, devicetree , LKML Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Nov 20, 2017 at 2:33 AM, Jonathan Cameron wrote: > On Thu, 2 Nov 2017 14:49:32 +0000 > Jonathan Cameron wrote: >> IIO is closed for this cycle anyway now. >> Otherwise, series looks good. >> >> Will pick up when back with my main PC as traveling for this week and >> next. > > Forgot to ask, do you want me to pick this up as a fix? > Also does it make sense to tag it for stable? > > If not I can pick it up for the coming cycle. Given the code changes > are small and well isolated I'm happy to do any of the 3 options, > it really depends on whether the rest of the platform works well enough > to be worth rushing these through? Without the clock driver upstream there's no rush to merge this. I'm still waiting on review from the clock guys. Please queue them for 4.16. Thanks! Cheers, Joel From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joel Stanley Subject: Re: [PATCH v2] iio: adc: aspeed: Deassert reset in probe Date: Mon, 20 Nov 2017 15:22:38 +1030 Message-ID: References: <20171031021203.18248-1-joel@jms.id.au> <20171102144932.00001e17@huawei.com> <20171119160318.41d7e85a@archlinux> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: In-Reply-To: <20171119160318.41d7e85a@archlinux> Sender: linux-iio-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Jonathan Cameron Cc: Jonathan Cameron , Philipp Zabel , Rick Altherr , Rob Herring , Hartmut Knaack , Lars-Peter Clausen , Peter Meerwald-Stadler , linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, devicetree , LKML List-Id: devicetree@vger.kernel.org On Mon, Nov 20, 2017 at 2:33 AM, Jonathan Cameron wrote: > On Thu, 2 Nov 2017 14:49:32 +0000 > Jonathan Cameron wrote: >> IIO is closed for this cycle anyway now. >> Otherwise, series looks good. >> >> Will pick up when back with my main PC as traveling for this week and >> next. > > Forgot to ask, do you want me to pick this up as a fix? > Also does it make sense to tag it for stable? > > If not I can pick it up for the coming cycle. Given the code changes > are small and well isolated I'm happy to do any of the 3 options, > it really depends on whether the rest of the platform works well enough > to be worth rushing these through? Without the clock driver upstream there's no rush to merge this. I'm still waiting on review from the clock guys. Please queue them for 4.16. Thanks! Cheers, Joel