From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1751723AbcAUAeb (ORCPT <rfc822;w@1wt.eu>);
	Wed, 20 Jan 2016 19:34:31 -0500
Received: from mailout2.w1.samsung.com ([210.118.77.12]:46259 "EHLO
	mailout2.w1.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1750871AbcAUAe3 (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Wed, 20 Jan 2016 19:34:29 -0500
X-AuditID: cbfec7f5-f79b16d000005389-30-56a02792bad0
Subject: Re: [PATCH 0/8] rtc: max77686: Extend driver and add max77802 support
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>,
        Javier Martinez Canillas <javier@osg.samsung.com>
References: <1453310088-29985-1-git-send-email-javier@osg.samsung.com>
 <20160121003047.GF3367@piout.net>
Cc: linux-kernel@vger.kernel.org, Kukjin Kim <kgene@kernel.org>,
        rtc-linux@googlegroups.com, Chanwoo Choi <cw00.choi@samsung.com>,
        Laxman Dewangan <ldewangan@nvidia.com>,
        linux-samsung-soc@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
        Olof Johansson <olof@lixom.net>, linux-arm-kernel@lists.infradead.org
From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Message-id: <56A02791.9010409@samsung.com>
Date: Thu, 21 Jan 2016 09:34:25 +0900
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.5.1
MIME-version: 1.0
In-reply-to: <20160121003047.GF3367@piout.net>
Content-type: text/plain; charset=windows-1252
Content-transfer-encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupkkeLIzCtJLcpLzFFi42I5/e/4Vd1J6gvCDM7NVLLouLaYyeLvpGPs
	Fte/PGe1ePN2DZPF6xeGFv2PXzNbLN23msVi0+NrrBaXd81hs5hxfh+Txanrn9ks9nd2MDrw
	ePz+NYnR48mmi4weeyaeZPPYtKqTzWPzknqPKyeaWD16m9+xeWzpv8vu0bdlFaPH501yAVxR
	XDYpqTmZZalF+nYJXBkbZk1nL2hnrdh15CNzA2MjSxcjJ4eEgInEnSt32CBsMYkL99aD2UIC
	SxklJi5U7GLkArKfMkr8e/CPCSQhLOAn0d/2A6iIg0NEoFBi7jZuiPosiRnLDrCB1DML7GKS
	aFjxEWwQm4CxxOblS8BsXgEtiVPXZoMtZhFQlTj48yaYLSoQIXG4s4sdokZQ4sfke2BxTgE9
	iY65y1lAdjED2fcvaoGEmQXkJTavecs8gVFgFpKOWQhVs5BULWBkXsUomlqaXFCclJ5rpFec
	mFtcmpeul5yfu4kREkFfdzAuPWZ1iFGAg1GJh/fGtflhQqyJZcWVuYcYJTiYlUR45VQWhAnx
	piRWVqUW5ccXleakFh9ilOZgURLnnbnrfYiQQHpiSWp2ampBahFMlomDU6qBMeWweJJXZfG5
	OlaxxR1Lcv9Y5So6nvkVudS8z2g1r0iVoYvpGRml1Oe2oSvPPc7OMXXaufKLd27qCtNLx5cZ
	dapGXC3qSChIV7QXqhdWvcl+KYi9pHhH8g/vsAVL569SWqLvcaJCktlzdbVs1WOOFYv7y6Wj
	PkmHfmCfPFtzmkdh50Xln9lKLMUZiYZazEXFiQDfGwhCnAIAAA==
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On 21.01.2016 09:30, Alexandre Belloni wrote:
>> I believe all patches should go through the RTC tree with proper acks or
>> wait until the RTC patches land to pick the defconfig changes.
>>
> 
> I think Olof would prefer the last patches to go through arm-soc.

That would be preferred but merging them before the 5/8 would cause a
loss of functionality on these defconfigs making it non-bisectable
approach. I think it would be good to preserve bisectability in that
matter so either:
1. a tag from RTC on top of which these patches would be applied in arm-soc,
2. take them to RTC tree with our acks.

Best regards,
Krzysztof