From: Mark Brown <broonie@opensource.wolfsonmicro.com> To: Russell King - ARM Linux <linux@arm.linux.org.uk> 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 19:10:06 +0100 [thread overview] Message-ID: <20120328181005.GC3232@opensource.wolfsonmicro.com> (raw) In-Reply-To: <20120328175613.GC22414@n2100.arm.linux.org.uk> [-- Attachment #1: Type: text/plain, Size: 1230 bytes --] On Wed, Mar 28, 2012 at 06:56:13PM +0100, Russell King - ARM Linux wrote: > On Wed, Mar 28, 2012 at 11:18:52AM +0100, Mark Brown wrote: > > 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. Well, I'd expect this stuff to be going via the pxa tree to arm-soc rather than via your tree anyway (which seems to be what's happening at this point) - half the point with arm-soc was to ensure you didn't have to deal with things like this. Quite frankly I thought the fixes had already been applied, they were posted and reviewed in good time for the merge window and the issues weren't being reported in -next any more; had someone asked I'd have applied them as I did with the equivalent stuff for u300. If they were being totally ignored I'd probably have applied them too, though perhaps not. [-- Attachment #2: Digital signature --] [-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH] ARM: pxa: fix regulator related build fail in magician_defconfig Date: Wed, 28 Mar 2012 19:10:06 +0100 [thread overview] Message-ID: <20120328181005.GC3232@opensource.wolfsonmicro.com> (raw) In-Reply-To: <20120328175613.GC22414@n2100.arm.linux.org.uk> On Wed, Mar 28, 2012 at 06:56:13PM +0100, Russell King - ARM Linux wrote: > On Wed, Mar 28, 2012 at 11:18:52AM +0100, Mark Brown wrote: > > 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. Well, I'd expect this stuff to be going via the pxa tree to arm-soc rather than via your tree anyway (which seems to be what's happening at this point) - half the point with arm-soc was to ensure you didn't have to deal with things like this. Quite frankly I thought the fixes had already been applied, they were posted and reviewed in good time for the merge window and the issues weren't being reported in -next any more; had someone asked I'd have applied them as I did with the equivalent stuff for u300. If they were being totally ignored I'd probably have applied them too, though perhaps not. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120328/6f4abb48/attachment.sig>
next prev parent reply other threads:[~2012-03-28 18:10 UTC|newest] Thread overview: 32+ 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 19:46 ` Paul Gortmaker 2012-03-06 20:01 ` Mark Brown 2012-03-06 20:01 ` Mark Brown 2012-03-06 20:49 ` [PATCH v2] " Paul Gortmaker 2012-03-06 20:49 ` Paul Gortmaker 2012-03-07 1:46 ` Paul Parsons 2012-03-07 1:46 ` Paul Parsons 2012-03-07 14:46 ` Paul Gortmaker 2012-03-07 14:46 ` Paul Gortmaker 2012-03-07 14:57 ` Mark Brown 2012-03-07 14:57 ` Mark Brown 2012-03-08 21:34 ` [PATCH] " Paul Gortmaker 2012-03-08 21:34 ` Paul Gortmaker 2012-03-09 2:47 ` Paul Parsons 2012-03-09 2:47 ` Paul Parsons 2012-03-14 8:38 ` Haojian Zhuang 2012-03-14 8:38 ` Haojian Zhuang 2012-03-14 12:30 ` Paul Gortmaker 2012-03-14 12:30 ` Paul Gortmaker 2012-03-14 12:32 ` Mark Brown 2012-03-14 12:32 ` Mark Brown 2012-03-28 9:43 ` Russell King - ARM Linux 2012-03-28 9:43 ` Russell King - ARM Linux 2012-03-28 10:18 ` Mark Brown 2012-03-28 10:18 ` Mark Brown 2012-03-28 13:36 ` Haojian Zhuang 2012-03-28 13:36 ` Haojian Zhuang 2012-03-28 17:56 ` Russell King - ARM Linux 2012-03-28 17:56 ` Russell King - ARM Linux 2012-03-28 18:10 ` Mark Brown [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=20120328181005.GC3232@opensource.wolfsonmicro.com \ --to=broonie@opensource.wolfsonmicro.com \ --cc=haojian.zhuang@gmail.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-next@vger.kernel.org \ --cc=linux@arm.linux.org.uk \ --cc=lost.distance@yahoo.com \ --cc=paul.gortmaker@windriver.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.