Received: by 2002:a25:c205:0:0:0:0:0 with SMTP id s5csp115078ybf; Wed, 26 Feb 2020 09:48:02 -0800 (PST) X-Google-Smtp-Source: APXvYqwfXxHveLnydNxF+flw79G6IB/grW02Pk8SalSzSaQsWXamUjN3ZMlX3KkuP38P9wyiDe8p X-Received: by 2002:a05:6808:3b2:: with SMTP id n18mr124579oie.146.1582739282424; Wed, 26 Feb 2020 09:48:02 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1582739282; cv=none; d=google.com; s=arc-20160816; b=JnByUItl+tPkZ+XfAwQEaxnlkbHDrVo+pBkitft85c9Ori8UnfWWEa9iRiT6XYdt0v w5ctNsJFh/4pIUb+pX3V9Rkzu2kEvQvzrzlmvRLaqyjmFaMSAnOhtBtZMEMp/Tuae91g +am5aJoqCYS3sGTfjDFJEkNmhrpePW+ecis34pygjdc+BwoYp5c9gcmkpuDu02V0FS4v vie4AZ9Q1w10IwpeYr4D97ZoXywUN+O6WcP87KcqSD7Oxu6EpJdzLTYBtbyC/AXn69aL w7nZvcs9vHzNLPockSnxZrvm5f/guZIUsD8D0C76ytV8PFezjphtUxPPeDyd/J+NRrP6 85AQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=UlkKnDdC74Y3bgeE6cEbPgpR1UfcBBF9OT0zkr0EUcg=; b=JO9iKLcs5FhbMD20dGsnKK4RxUYxBdcuZd3NZWsgxZN1Cim+tPblLXLHuLEHTWJxjL fNWDmj6GHHLECMr8JubPuOivt1Nodgb2wmz8MqSpia9cCvxwluGjcTSDG+6ZO4oCilzi iFYfQsqSRvM8vHGUbYVrb3LjH0Tc+R0haf2HmsWLbJl68ZiA84HustaQJOPmE2cpc6jz Z0ymcLDRF8BEnYYUWCXZA2rNGNFz9OdpBH1y+OEMd5pkJ4mB1+mkLBTUJ2rYMaccrJZE +/zxwM9baIKm2y67hu67deZSgIEfQtWWyICzQRgrCIaqcDUg2+J6r5iCmdiUxt2nUw/d NkNg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=BGEEl7rm; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x186si1440933oig.209.2020.02.26.09.47.50; Wed, 26 Feb 2020 09:48:02 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=BGEEl7rm; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726974AbgBZRqL (ORCPT + 99 others); Wed, 26 Feb 2020 12:46:11 -0500 Received: from mail-wr1-f66.google.com ([209.85.221.66]:34319 "EHLO mail-wr1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726151AbgBZRqK (ORCPT ); Wed, 26 Feb 2020 12:46:10 -0500 Received: by mail-wr1-f66.google.com with SMTP id z15so4214259wrl.1 for ; Wed, 26 Feb 2020 09:46:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=UlkKnDdC74Y3bgeE6cEbPgpR1UfcBBF9OT0zkr0EUcg=; b=BGEEl7rmEJYfaMnxUESPvUOgeSbE0vRSPk4AeQjFIwdfBqYXStXjR+rObFWAaQbqg1 bdOXNcZYOR+hFebyfy7thu2k30LD1Epy2eOgsjn2SuwHoRCJF0Kr0DjH22TAgWxY41Dc C0PcGYnjSiPRM14Hw2u0Z+2cwUCdQyjwFvYmSiRwtnHdOIcJvaLybuk0VDxnmE+PZJnn 4QRNIzz04bdlHohCuatcxOucvZ/Blllhhelky/i5lwYCXd4SKOspi5gFSfrWYCblUndd xEShQS4T63fHgE3ImaZRxkrl8P2+FnSF52tCc/zApvyPYTpmoo/A2s2FttSQYn0waYFI xy6A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=UlkKnDdC74Y3bgeE6cEbPgpR1UfcBBF9OT0zkr0EUcg=; b=JzH07hYoUZJTO1iaYglmDUqHmYZ+sF7Wxn3Hy5jjOXjCnKamqS5EsDRJTog7RAdXVi K5qDaPRwlMU+w7q/4+s1QoT7V90XwMCeY3iJCO6sPGAXOwWjpZcW++0jlC1NoIW00Zti nu15jfUvmvrWyEjlZrpp4gFQ85MtysD3/Y4/VYfzm0r2IYjNJC5pqamQq9t5ii1FkrzE wKdfZFW0gAJHy2Ja+ewAMsFhkSh5CPdQKl6C2jPltEMF9ZB6UkJ69V5k29R/eBU+Mvym HMuNrvvLHtBT+lOO0Yimr2yceHODTsBWiwVTqXd/FO/sLYIZam049I+0IWzuDu4cjCFz TOfA== X-Gm-Message-State: APjAAAUPOsMcGG83zBXAmcG4SH4KQoaEnyPkVY8+2jhv06Bmgtm+nRrE 4cjl+MlsuRgcySixseA/qtKzhg== X-Received: by 2002:adf:fc12:: with SMTP id i18mr6690147wrr.354.1582739168790; Wed, 26 Feb 2020 09:46:08 -0800 (PST) Received: from dell ([2.31.163.122]) by smtp.gmail.com with ESMTPSA id d76sm3849939wmd.39.2020.02.26.09.46.07 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 26 Feb 2020 09:46:08 -0800 (PST) Date: Wed, 26 Feb 2020 17:46:40 +0000 From: Lee Jones To: Andreas Kemnade Cc: knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net, b.galvani@gmail.com, linus.walleij@linaro.org, linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org, phh@phh.me, stefan@agner.ch, letux-kernel@openphoenux.org, jic23@kernel.org Subject: Re: [PATCH v5 1/2] mfd: rn5t618: add ADC subdevice for RC5T619 Message-ID: <20200226174640.GR3494@dell> References: <20200223131638.12130-1-andreas@kemnade.info> <20200223131638.12130-2-andreas@kemnade.info> <20200226154055.GQ3494@dell> <20200226174914.047667d5@kemnade.info> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20200226174914.047667d5@kemnade.info> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 26 Feb 2020, Andreas Kemnade wrote: > On Wed, 26 Feb 2020 15:40:55 +0000 > Lee Jones wrote: > > > On Sun, 23 Feb 2020, Andreas Kemnade wrote: > > > > > This adds a subdevice for the ADC in the RC5T619 > > > > > > Signed-off-by: Andreas Kemnade > > > --- > > > depends on: > > > https://lore.kernel.org/lkml/20191220122416.31881-1-andreas@kemnade.info/ > > > > > > Changes in v3: > > > re-added it to the series because of > > > "Oh, it looks like there was a conflict. Could you collect any Acks > > > (including mine) rebase and resend please?" > > > > Looks like there is still a conflict. Sure, it's not a complicated > > fix, but that's beside the point. What tree is this set based on? > > > It must be applied on top of my rc5t619 rtc series here: > https://lore.kernel.org/lkml/20191220122416.31881-1-andreas@kemnade.info/ > > I expected it to make it into 5.6 and when I first sent the RTC series > (in October) I had no idea when I will continue with other stuff. > > That is why I sent this ADC series separately, also to give the IIO > maintainer plenty of time to review. If a patch-set can or should be applied on its own, you should send it based on an upstream commit, or else things like this happen. My advice would be to maintain topic branches, each based on an upstream release, which you can merge together into an integration branch for full coverage testing. > Do you want me to resend all that pending stuff together in one series? > I have little experience with this multi-subdevice process. It makes more sense to rebase this set onto the latest full release and resubmit this set on its own. -- Lee Jones [李琼斯] Linaro Services Technical Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog