From: Russell King - ARM Linux <linux@arm•linux.org.uk>
To: Mark Brown <broonie@opensource•wolfsonmicro.com>
Cc: Shawn Guo <shawn.guo@linaro•org>,
Paul Gortmaker <paul.gortmaker@windriver•com>,
linus.walleij@linaro•org, linux-next@vger•kernel.org,
linux-arm-kernel@lists•infradead.org
Subject: Re: linux-next: "amba: Remove AMBA level regulator support" commit.
Date: Fri, 13 Apr 2012 13:19:14 +0100 [thread overview]
Message-ID: <20120413121914.GN24211@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20120413120706.GT3168@opensource.wolfsonmicro.com>
On Fri, Apr 13, 2012 at 01:07:07PM +0100, Mark Brown wrote:
> On Fri, Apr 13, 2012 at 11:49:00AM +0100, Russell King - ARM Linux wrote:
>
> > What I want is something that doesn't cause a regression for 3.4.
>
> Oh, and note that there's already a fix for the missing header although
> with all the git trees I've no idea what the process is for getting it
> into mainline.
That really doesn't make any difference about whether I can push 7366/1
as is or not. If the fix for the missing header is going through some
other git tree, I can't push 7366/1 until that fix has gone in - and
I'm not going to be tracking when that happens.
TBH, its something that _you_ need to manage - you created this regression
in the first place by changing the regulator API without first reviewing
all the callsites. Grep is a wonderful tool for finding those. So I'll
leave it entirely up to you to figure out how to fix the AMBA regression
you caused in a sane way in -rc - and without causing any additional
regressions by doing so.
If you want me to apply 7367/1 instead, then please say so directly. If
you want 7366/1 plus the header file fixed, then that needs to be figured
out.
next prev parent reply other threads:[~2012-04-13 12:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 1:22 linux-next: "amba: Remove AMBA level regulator support" commit Paul Gortmaker
2012-04-13 2:01 ` Shawn Guo
2012-04-13 10:32 ` Russell King - ARM Linux
2012-04-13 10:44 ` Mark Brown
2012-04-13 10:49 ` Russell King - ARM Linux
2012-04-13 11:25 ` Mark Brown
2012-04-13 12:17 ` Fabio Estevam
2012-04-13 12:07 ` Mark Brown
2012-04-13 12:19 ` Russell King - ARM Linux [this message]
2012-04-13 14:04 ` Mark Brown
2012-04-13 12:30 ` Linus Walleij
2012-04-13 8:37 ` Mark Brown
2012-04-13 12:26 ` Linus Walleij
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=20120413121914.GN24211@n2100.arm.linux.org.uk \
--to=linux@arm$(echo .)linux.org.uk \
--cc=broonie@opensource$(echo .)wolfsonmicro.com \
--cc=linus.walleij@linaro$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=paul.gortmaker@windriver$(echo .)com \
--cc=shawn.guo@linaro$(echo .)org \
/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