From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750937AbdAaXGV (ORCPT ); Tue, 31 Jan 2017 18:06:21 -0500 Received: from mail-wm0-f41.google.com ([74.125.82.41]:37406 "EHLO mail-wm0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750847AbdAaXGT (ORCPT ); Tue, 31 Jan 2017 18:06:19 -0500 Subject: Re: Optional regulators in bulk operations - reverted patch To: bjorn.andersson@linaro.org References: <8f3551cb-a499-5c9d-1c11-4ce66b093c44@gmail.com> Cc: Mark Brown , Linux Kernel Mailing List From: Heiner Kallweit Message-ID: Date: Tue, 31 Jan 2017 22:59:24 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 In-Reply-To: <8f3551cb-a499-5c9d-1c11-4ce66b093c44@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am 31.01.2017 um 22:43 schrieb Heiner Kallweit: > Hi Bjorn, > > I just came across a use case where I wanted to deal with optional > regulators in bulk operations. I was about to submit a related > patch when I saw that you submitted basically the same in > 3ff3f518a135 "regulator: Make bulk API support optional supplies" > and reverted it later stating that you misunderstood the API. > > How does this extension break the API? To me it sounds like a > neat feature. > > The only thing I can think of if that we have to assume that > struct regulator_bulk_data is zero-initialized to ensure > backwards-compatibility (use "normal" get as default). > > Rgds, Heiner > Sorry for the noise, I got it meanwhile.