From: Heiner Kallweit <hkallweit1@gmail.com>
To: bjorn.andersson@linaro.org
Cc: Mark Brown <broonie@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Optional regulators in bulk operations - reverted patch
Date: Tue, 31 Jan 2017 22:59:24 +0100 [thread overview]
Message-ID: <b0594876-fa4c-9d8c-5c11-960ceab43676@gmail.com> (raw)
In-Reply-To: <8f3551cb-a499-5c9d-1c11-4ce66b093c44@gmail.com>
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.
prev parent reply other threads:[~2017-01-31 23:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 21:43 Heiner Kallweit
2017-01-31 21:59 ` Heiner Kallweit [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b0594876-fa4c-9d8c-5c11-960ceab43676@gmail.com \
--to=hkallweit1@gmail.com \
--cc=bjorn.andersson@linaro.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®