ARM MSM updates for 2.6.35-rc1
in [Kernel]
|
Prev: [PATCH] checkkconfigsymbols.sh: Kconfig symbols sometimes have lowercase letters
Next: failed command FLUSH CACHE EXT (was: Re: via 8237 sata errors)
From: Daniel Walker on 2 Jun 2010 17:00 On Thu, 2010-05-27 at 14:52 -0700, Daniel Walker wrote: > Hi Linus, > > Here's a couple of simple patches. One fixes a compile failure in > certain situations, and the other is just dead code removal. > > Daniel > > > The following changes since commit 7b52161d14fa8a22a2387f4aa2fb7b854587830d: > > msm: 7x30 Kconfig and makefile changes (2010-05-13 16:08:55 -0700) > > are available in the git repository at: > git://codeaurora.org/quic/kernel/dwalker/linux-msm.git msm-core Don't forget about this one! Or was something wrong with it? Daniel -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Linus Torvalds on 2 Jun 2010 17:40 On Wed, 2 Jun 2010, Daniel Walker wrote: > > Don't forget about this one! Or was something wrong with it? I got a bit frustrated with ten different ARM pulls per day at one point. There's something wrong with ARM development. The amount of pure noise in the patches is incredibly annoying. Right now, ARM is already (despite me not reacting to some of the flood) 55% of all arch/ changes since 2.6.34, and it's all pointless churn in arch/arm/configs/ arch/arm/mach-xyz arch/arm/plat-blah and at a certain point in the merge window I simply could not find it in me to care about it any more. Do you guys at all talk about this problem? Have any of the ARM people bothered to look at the arch/arm diffs and see how mind-deadening they are? I try to look through these kinds of things when I pull, but after a million lines of pure noise, it gets old pretty quickly. Somehow, I can't believe that you need thousands of lines for each random arch/arm/mach-xyz (yeah, some very few of them are smaller). For a taste of the mind-deadening experience, just do for i in arch/arm/mach-* do echo $i; wc -l $(git ls-files $i) done | less -S and imagine being on the receiving side of that. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Linus Torvalds on 2 Jun 2010 17:50 On Wed, 2 Jun 2010, Linus Torvalds wrote: > > I got a bit frustrated with ten different ARM pulls per day at one point. In other words - when I do a "git pull", I really want to feel like there is some point to it. When I get ten different ARM maintainers asking me to pull stuff that just looks like noise, I'm just not getting those warm and fuzzies about them. I'm also getting the feeling that now that different arch sub-architecture maintainers all try to get their stuff in through me, things have actually gotten worse - there's even less feeling of "somebody is actually trying to keep track of all this stuff". I understand why rmk wasn't happy. I'm also not really happy. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Daniel Walker on 2 Jun 2010 18:00 On Wed, 2010-06-02 at 14:39 -0700, Linus Torvalds wrote: > > On Wed, 2 Jun 2010, Linus Torvalds wrote: > > > > I got a bit frustrated with ten different ARM pulls per day at one point. > > In other words - when I do a "git pull", I really want to feel like there > is some point to it. When I get ten different ARM maintainers asking me to > pull stuff that just looks like noise, I'm just not getting those warm and > fuzzies about them. > > I'm also getting the feeling that now that different arch sub-architecture > maintainers all try to get their stuff in through me, things have actually > gotten worse - there's even less feeling of "somebody is actually trying > to keep track of all this stuff". > > I understand why rmk wasn't happy. I'm also not really happy. Should all us ARM sub-architecture maintainers get together and make a jumbo pull request with everything merged together? Like someone, not you or RMK, would take all the sub-architecture requests and put them into a single pull request w/ lots of details as to what it all is .. I know that doesn't solve what you said in the original email, how we develop. One thing to remember is that we have tons of ARM device to manage, and lots of chip manufactures .. So ARM is pretty diverse. I'm not saying we're all perfect however. Daniel -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Daniel Walker on 2 Jun 2010 18:40
On Wed, 2010-06-02 at 14:27 -0700, Linus Torvalds wrote: > > On Wed, 2 Jun 2010, Daniel Walker wrote: > > > > Don't forget about this one! Or was something wrong with it? > > I got a bit frustrated with ten different ARM pulls per day at one point. > > There's something wrong with ARM development. The amount of pure noise in > the patches is incredibly annoying. Right now, ARM is already (despite me > not reacting to some of the flood) 55% of all arch/ changes since 2.6.34, > and it's all pointless churn in > > arch/arm/configs/ > arch/arm/mach-xyz > arch/arm/plat-blah > > and at a certain point in the merge window I simply could not find it in > me to care about it any more. > > Do you guys at all talk about this problem? Have any of the ARM people > bothered to look at the arch/arm diffs and see how mind-deadening they > are? I try to look through these kinds of things when I pull, but after a > million lines of pure noise, it gets old pretty quickly. There's room for the sub-architectures to combine stuff. I think there is work going on to do that (at some level). > Somehow, I can't believe that you need thousands of lines for each random > arch/arm/mach-xyz (yeah, some very few of them are smaller). I'm not an authority by any means, but every time there is a new device released (which is often) you get a new file under some mach-xyz directory, or some large modification to an already existing file. Plus a config file potentially. It's a little bit like the wild west, and seems way wilder than x86 every was. I think from the sub-architecture maintainer perspective the pain is all hidden behind the Linus curtain , or RMK curtain or the some other maintainer curtain. So we don't really talk about it that often. I thought you we're totally happy with the situation .. If you have some idea's for fixing things, I'm all ears along with my faithful sub-architecture maintainer brothers. Daniel -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |