Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1381225 > unrolled thread
| Started by | Stephen Rothwell <sfr@canb.auug.org.au> |
|---|---|
| First post | 2016-04-18 05:50 +0200 |
| Last post | 2016-04-18 11:20 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.kernel
linux-next: build warning after merge of the regulator tree Stephen Rothwell <sfr@canb.auug.org.au> - 2016-04-18 05:50 +0200
Re: linux-next: build warning after merge of the regulator tree Mark Brown <broonie@kernel.org> - 2016-04-18 11:20 +0200
| From | Stephen Rothwell <sfr@canb.auug.org.au> |
|---|---|
| Date | 2016-04-18 05:50 +0200 |
| Subject | linux-next: build warning after merge of the regulator tree |
| Message-ID | <rp8mg-7cT-53@gated-at.bofh.it> |
Hi all,
After merging the regulator tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
drivers/gpu/drm/msm/dsi/dsi_host.c: In function 'dsi_regulator_init':
drivers/gpu/drm/msm/dsi/dsi_host.c:329:3: warning: 'regulator_can_change_voltage' is deprecated [-Wdeprecated-declarations]
if (regulator_can_change_voltage(s[i].consumer)) {
^
and several more ...
Introduced by commit
6a0028b3dd67 ("regulator: Deprecate regulator_can_change_voltage()")
In the future, please fix up all the current users of an interface
*before* marking it deprecated. All these extra warnings just muddy the
"real" warnings ...
--
Cheers,
Stephen Rothwell
[toc] | [next] | [standalone]
| From | Mark Brown <broonie@kernel.org> |
|---|---|
| Date | 2016-04-18 11:20 +0200 |
| Message-ID | <rpdvA-2TT-7@gated-at.bofh.it> |
| In reply to | #1381225 |
[Multipart message — attachments visible in raw view] — view raw
On Mon, Apr 18, 2016 at 01:43:51PM +1000, Stephen Rothwell wrote: > In the future, please fix up all the current users of an interface > *before* marking it deprecated. All these extra warnings just muddy the > "real" warnings ... Ideally but sadly all the issues are in the graphics stack and while they seem relatively responsive to build issues there seems to be some strange way of working there which means that getting changes integrated or responses when issues like this come up has always been extremely difficult and unfortunately cut'n'paste also seems to be quite common (most of these look like they came from one place) so something to try to at least give people pause for thought when they introduce new issues seems sensible. I really wish I could figure out what's going on there.
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web