From: Russell King - ARM Linux <linux@arm•linux.org.uk>
To: Mark Brown <broonie@opensource•wolfsonmicro.com>
Cc: Paul Gortmaker <paul.gortmaker@windriver•com>,
linux-next@vger•kernel.org, linux-arm-kernel@lists•infradead.org,
Haojian Zhuang <haojian.zhuang@gmail•com>,
lost.distance@yahoo•com
Subject: Re: [PATCH] ARM: pxa: fix regulator related build fail in magician_defconfig
Date: Wed, 28 Mar 2012 18:56:13 +0100 [thread overview]
Message-ID: <20120328175613.GC22414@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20120328101852.GE3232@opensource.wolfsonmicro.com>
On Wed, Mar 28, 2012 at 11:18:52AM +0100, Mark Brown wrote:
> On Wed, Mar 28, 2012 at 10:43:51AM +0100, Russell King - ARM Linux wrote:
> > On Wed, Mar 14, 2012 at 12:32:36PM +0000, Mark Brown wrote:
>
> > > Yes, that's what you should do. Calling dev_name() is only possible if
> > > you have the struct device and removing the need for the struct device
> > > is exactly what we're trying to avoid here.
>
> > So what the hell is happening here to fix the breakage which the
> > regulator tree caused in mainline? From this thread, it looks like
> > it's been known about since 8th March which is now twenty days ago,
> > and it's still broken.
>
> Yes, please at least apply Paul's patches - honestly, given how old
> these boards are and the general lack of activity I'd rather expect that
> the only thing anyone's doing with them these days is build tests.
Is that a reason to push breakage to them upstream? No. Please take
Paul's patches to fix the breakage which was introduced through your
tree yourself. I've got enough problems this merge window to deal with
without having to add further patches to my tree.
Thanks.
next prev parent reply other threads:[~2012-03-28 17:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 19:46 [PATCH] ARM: pxa: fix regulator related build fail in magician_defconfig Paul Gortmaker
2012-03-06 20:01 ` Mark Brown
2012-03-06 20:49 ` [PATCH v2] " Paul Gortmaker
2012-03-07 1:46 ` Paul Parsons
2012-03-07 14:46 ` Paul Gortmaker
2012-03-07 14:57 ` Mark Brown
2012-03-08 21:34 ` [PATCH] " Paul Gortmaker
2012-03-09 2:47 ` Paul Parsons
2012-03-14 8:38 ` Haojian Zhuang
2012-03-14 12:30 ` Paul Gortmaker
2012-03-14 12:32 ` Mark Brown
2012-03-28 9:43 ` Russell King - ARM Linux
2012-03-28 10:18 ` Mark Brown
2012-03-28 13:36 ` Haojian Zhuang
2012-03-28 17:56 ` Russell King - ARM Linux [this message]
2012-03-28 18:10 ` Mark Brown
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=20120328175613.GC22414@n2100.arm.linux.org.uk \
--to=linux@arm$(echo .)linux.org.uk \
--cc=broonie@opensource$(echo .)wolfsonmicro.com \
--cc=haojian.zhuang@gmail$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=lost.distance@yahoo$(echo .)com \
--cc=paul.gortmaker@windriver$(echo .)com \
/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