From: Mark Brown <broonie@kernel•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Liam Girdwood <lgirdwood@gmail•com>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: build warning after merge of the regulator tree
Date: Mon, 18 Apr 2016 10:15:23 +0100 [thread overview]
Message-ID: <20160418091523.GJ3217@sirena.org.uk> (raw)
In-Reply-To: <20160418134351.087823c5@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 803 bytes --]
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-04-18 9:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 3:43 linux-next: build warning after merge of the regulator tree Stephen Rothwell
2016-04-18 9:15 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-23 4:52 Stephen Rothwell
2024-10-23 4:51 Stephen Rothwell
2020-01-10 2:41 Stephen Rothwell
2018-10-02 3:07 Stephen Rothwell
2018-10-02 6:16 ` Matti Vaittinen
2018-10-02 6:25 ` Stephen Rothwell
2018-10-02 6:43 ` Matti Vaittinen
2018-10-02 13:02 ` Mark Brown
2015-10-07 2:45 Stephen Rothwell
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=20160418091523.GJ3217@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=lgirdwood@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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