Received: by 10.223.185.116 with SMTP id b49csp2659441wrg; Mon, 5 Mar 2018 06:46:14 -0800 (PST) X-Google-Smtp-Source: AG47ELshBUeOjxc/5HlnYFvkR4XfyId07wJbSC25kUX9BovpiNkjsiSaV0QN+MuFi42QGnw/UdFX X-Received: by 10.101.74.74 with SMTP id a10mr12842373pgu.32.1520261174279; Mon, 05 Mar 2018 06:46:14 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1520261174; cv=none; d=google.com; s=arc-20160816; b=Gk49Db4dv8AS63PyXeUKyr1mRAi0U0q3Bhm/LcSbn51phFeYzwFMRKCFWxd1e9PiL7 pGl6RLfafD8GSsJ4GinqhvhOWgZGM9Tb80R4GnOc+G3ZxzZC4Fs/GhrQ2BdPrgvRObPy 0Mme0xnOGQEF3+JWOkMfmW8FzB4t5/v+E4RnqhyX8r6O7NUmluaBDncsa12ySGD7dLFw fCJM/pASK5VV5zpWWQr+cSid40Adr/M+YcGSn2Z0peMsvaJjdd5YvPRFo+dhQfcRAL1D WdZ57UcU741M7Ee2jdxyBHvggyg2KBk9JXLkwKzssbe0JmcMLnRcq7SB81T0yjOxYoww Vvbw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:organization:from:references:to:subject:cc :arc-authentication-results; bh=la+HdAC2enIU2MvQi+FayoGan2W9o/coAiFMnagrwNk=; b=wb0cGc91BKGhQsMjKhoHn7Et21EZFU4OEkdAqQNuYwQoL1SMlE/6qYC+ushFbffIZv lDq3CDRT3WYsy8KsDFngvgdAyXQHF+8Z7tbDSfP6rQkZh9YR+KS3gA/5GJpzY5tR2ATk j2/GHNLVpn2ywIuySwNq9BJ6A4Na+W9OB8Q7msp8wFOKHfiP2ZzoOfHITK/acWYad0/R CW0GushWhOlrZ0yun9vPNElb9D9N2yc5ZYfgIE+OL9T6wqjRV+hbyYix7vh4SIUd/sFd zB6r+D0ilTjy2nWtylwqr/IhAY9ItlLGakEMaYV+rXD+snN6HZ5xeqwuAoTz9NRuo8OT W3IA== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e11si8413675pgr.231.2018.03.05.06.45.59; Mon, 05 Mar 2018 06:46:14 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752076AbeCEOoB (ORCPT + 99 others); Mon, 5 Mar 2018 09:44:01 -0500 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:51280 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751294AbeCEOn5 (ORCPT ); Mon, 5 Mar 2018 09:43:57 -0500 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 80DB21529; Mon, 5 Mar 2018 06:43:57 -0800 (PST) Received: from [10.1.211.34] (unknown [10.1.211.34]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 9B9DE3F25C; Mon, 5 Mar 2018 06:43:55 -0800 (PST) Cc: Sudeep Holla , ALKML , LKML , DTML , Alexey Klimov , Greg Kroah-Hartman , Arnd Bergmann Subject: Re: [PATCH v6 13/20] firmware: arm_scmi: refactor in preparation to support per-protocol channels To: Jonathan Cameron References: <1519403030-21189-1-git-send-email-sudeep.holla@arm.com> <1519403030-21189-14-git-send-email-sudeep.holla@arm.com> <20180305153549.00000f39@huawei.com> From: Sudeep Holla Organization: ARM Message-ID: <1e824524-5ed3-dfbc-b2fb-6a15631b44cd@arm.com> Date: Mon, 5 Mar 2018 14:43:52 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180305153549.00000f39@huawei.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 05/03/18 14:35, Jonathan Cameron wrote: > On Fri, 23 Feb 2018 16:23:43 +0000 > Sudeep Holla wrote: > >> In order to support per-protocol channels if available, we need to >> factor out all the mailbox channel information(Tx/Rx payload and >> channel handle) out of the main SCMI instance information structure. >> >> This patch refactors the existing channel information into a separate >> chan_info structure. >> >> Cc: Arnd Bergmann >> Cc: Greg Kroah-Hartman >> Signed-off-by: Sudeep Holla > A little odd to present a series to mainline that does a fairly important > refactor mid way through. Why not push this down to the start and always support > the separate chan_info structure? > Since the development started long back and this was added later, I preferred to keep functionality working and didn't want to push change down in the stack. -- Regards, Sudeep