Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1571157
| From | Heiner Kallweit <hkallweit1@gmail.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Optional regulators in bulk operations - reverted patch |
| Date | 2017-01-31 22:50 +0100 |
| Message-ID | <t5Otk-5NY-13@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
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
Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
Optional regulators in bulk operations - reverted patch Heiner Kallweit <hkallweit1@gmail.com> - 2017-01-31 22:50 +0100 Re: Optional regulators in bulk operations - reverted patch Heiner Kallweit <hkallweit1@gmail.com> - 2017-02-01 00:10 +0100
csiph-web