{"shas":[["5457cc20d3abc1d88d76a87e6fe88d66c2688f33","60c6d277a8bd81de7fdde19201bf9c58a3df08f4@derhofbauer.at","Initial import from marvel-2.6.35-crc.tar.gz","Alexander Hofbauer"],["d0eac274a08e0718013fa15832d640ddba5eb637","0f41a0b3b760b54df703e860e40fef1c388ed2c5@gmail.com","msm7227: Overclocking support to 864MHz\n\nfix stepping from 400 to 768\n\nadded all frequencies although them commented out.\n\nfix so all frequencies should work together","jp"],["0ef784b519202e0f9e37eea741aa1805077ff3f3","b23d0c7bb708db91c8b9415ae7caad6fe333f717@google.com","md: dm-crypt: Add option to re-use a new global work-queue.\n\nTypically, dm-crypt instances each have their own set of kcrypt/kcrypt_io\nwork-queues. This patch adds an option which will create one set of\nwork-queues on init, and re-uses them for all dm-crypt target instances\nin order to cut down on resource overhead on embedded systems.\n\nNOTE: If you use stacked dm-crypt instances, then enabling this option\nmay cause a deadlock.\n\nCc: Milan Broz <mbroz@redhat.com>\nCc: Brian Swetland <swetland@google.com>\nCc: Andrew Morton <apkm@linux-foundation.org>\nCc: Christophe Saout <christophe@saout.de>\nSigned-off-by: San Mehat <san@google.com>","San Mehat"],["ff8bcb273828fcee2b97d7ce7131b09601814c94","7f5bb03cf507c861269be561971108be8f37d832@chemlab.org","msm: flashlight: Add DEATH_RAY mode\n\nConflicts:\n\n\tarch/arm/mach-msm/msm_flashlight.c","Steve Kondik"],["27a1417c8df06b12f1a2486a2d5f68f28e41b131","7f5bb03cf507c861269be561971108be8f37d832@discord.hmsinc.com","Add USB_ANDROID_RNDIS_WCEIS option.\n\nChange-Id: I85973ebfcbfae6b401fb8b402842309c72655149\nSigned-off-by: Mike Lockwood <lockwood@android.com>","Steve Kondik"],["634136e4b630932a0dbb2c719dd8078f7d5eca13","470bc578162732ac7f9d387d34c4af4ca6e1b6f7@android.com","[ARM] msm: kgsl: Remove support for mmap from the kgsl driver.\n\nThe mmap(2) functionality of kgsl is no longer used, and it had a\nbug that would crash the kernel when mmap(2) was called with\n\"odd\" parameters.  So we have removed the mmap functionality.\nIf for some reason in the future you want to resurrect this,\nmake sure memdesc is properly initialized in all paths through\nthe kgsl_mmap() routine.\n\nSigned-off-by: Ken Sumrall <ken@android.com>","Ken Sumrall"],["6e1634e07dc423d0a30259fd71df27e05cdb957d","af9cbceb8388e2170881d17f5ca88833c5c37ed6@quicinc.com","msm_kgsl: Restore the shader when CTXT_FLAGS_SHADER_RESTORE flag is set","Shubhraprakash Das"],["1a29c10f05ef1ab8490c50c2cd387b15bb5d41b9","af9cbceb8388e2170881d17f5ca88833c5c37ed6@quicinc.com","msm_kgsl: Optimize TLB flushing\n\nOnly flush TLB when it is absolutely nessasary as opposed to\nflushing it on every map and unmap","Shubhraprakash Das"],["41dbf0f067002c1824d0ee290cf78e126c074de1","7f5bb03cf507c861269be561971108be8f37d832@chemlab.org","modules: Add CONFIG_MODULE_FORCE_VERMAGIC\n\nVery evil option for allowing force-loading of modules with bad\nvermagic. Normally this should never be required.","Steve Kondik"],["b836571ec7365c655984d2c6f3a9a341c9bd9899","7f5bb03cf507c861269be561971108be8f37d832@chemlab.org","pmem: Add PMEM_CACHE_FLUSH ioctl.","Steve Kondik"],["83295a9ab2a2261cd8b321f7cf4d24e305ca279b","a17fed27eaa842282862ff7c1b9c8395a26ac320@android.com","cpufreq: interactive: New 'interactive' governor\n\nThis governor is designed for latency-sensitive workloads, such as\ninteractive user interfaces.  The interactive governor aims to be\nsignificantly more responsive to ramp CPU quickly up when CPU-intensive\nactivity begins.\n\nExisting governors sample CPU load at a particular rate, typically\nevery X ms.  This can lead to under-powering UI threads for the period of\ntime during which the user begins interacting with a previously-idle system\nuntil the next sample period happens.\n\nThe 'interactive' governor uses a different approach. Instead of sampling\nthe CPU at a specified rate, the governor will check whether to scale the\nCPU frequency up soon after coming out of idle.  When the CPU comes out of\nidle, a timer is configured to fire within 1-2 ticks.  If the CPU is very\nbusy from exiting idle to when the timer fires then we assume the CPU is\nunderpowered and ramp to MAX speed.\n\nIf the CPU was not sufficiently busy to immediately ramp to MAX speed, then\nthe governor evaluates the CPU load since the last speed adjustment,\nchoosing the highest value between that longer-term load or the short-term\nload since idle exit to determine the CPU speed to ramp to.\n\nA realtime thread is used for scaling up, giving the remaining tasks the\nCPU performance benefit, unlike existing governors which are more likely to\nschedule rampup work to occur after your performance starved tasks have\ncompleted.\n\nThe tuneables for this governor are:\n/sys/devices/system/cpu/cpufreq/interactive/min_sample_time:\nThe minimum amount of time to spend at the current frequency before\nramping down. This is to ensure that the governor has seen enough\nhistoric CPU load data to determine the appropriate workload.\nDefault is 80000 uS.\n/sys/devices/system/cpu/cpufreq/interactive/go_maxspeed_load\nThe CPU load at which to ramp to max speed.  Default is 85.\n\nChange-Id: Ib2b362607c62f7c56d35f44a9ef3280f98c17585\nSigned-off-by: Mike Chan <mike@android.com>\nSigned-off-by: Todd Poynor <toddpoynor@google.com>\nBug: 3152864","Mike Chan"],["b857e1477f3bc9bbee70224483438e0875659e9f","57cb0497077c01018e8c022963d2feeac2e977b4@google.com","cpufreq interactive governor save/restore IRQs around cpumask spinlocks\n\nNeed to use irqsave/restore spin locking for cpumasks since these\nare accessed in timers and in thread context.\n\nChange-Id: I4a53eaf0ced7e73b445feddba90ec11482de9126\nSigned-off-by: Todd Poynor <toddpoynor@google.com>","Todd Poynor"],["695cb926382e7cccf1330f5756fe5b870cb02ca5","57cb0497077c01018e8c022963d2feeac2e977b4@google.com","cpufreq interactive governor: fix crash on CPU shutdown\n\nDon't reference the saved copy of the CPU's cpufreq policy\npointer after the governor has been stopped for the CPU.\n\nWhen the governor is stopped for a CPU:\n\n* Use del_timer_sync() to wait for a currently-running timer\nfunction to stop.\n\n* Delete the timer when the governor is stopped for the\nassociated CPU, not when the last CPU is stopped.\n\n* Flush any speed down work ongoing.\n\n* Reset the timestamp that is used to tell if the timer function\nhas had a chance to run since last idle exit.\n\nCheck the governor enabled flag for the CPU before re-arming the\ntimer from within the timer function and at idle exit (in case\nstopping the governor at runtime).\n\nCheck the governor enabled flag for the CPU in the worker\nfunction and thread before using the policy pointer.  (There is\nstill a tiny window in the thread that needs more work to close.)\n\nChange-Id: Ifaddf7a495a8dae15a579a57bdc654f7c47f6ada\nSigned-off-by: Todd Poynor <toddpoynor@google.com>","Todd Poynor"],["ac002914ff23d3cf0b8b7b17437fd8a2bf8b9bd2","57cb0497077c01018e8c022963d2feeac2e977b4@google.com","ARM: Stop irqsoff trace on return to user\n\nIf the irqsoff tracer is in use, stop tracing the interrupt disable\ninterval when returning to userspace.  Tracing userspace execution\ntime as interrupts disabled time is not helpful for kernel\nperformance analysis purposes.  Only do so if the irqsoff tracer\nis enabled, to avoid overhead purely for lockdep, which doesn't\ncare.\n\nChange-Id: I74cde7dd0c4c3a783af34e76bd4efc1f85315abe\nSigned-off-by: Todd Poynor <toddpoynor@google.com>","Todd Poynor"],["2adc68fb3df7ab40503d386cd982bb54fc2f4284","ecd1f14f7c1c6dc7a40210bdcc3810e0107ecbc8@android.com","input: evdev: Add missing wake_lock_destroy\n\nChange-Id: Ief1ef44d98a197e5b457f5e8617c413e76e3c6d2\nSigned-off-by: Benoit Goby <benoit@android.com>","Benoit Goby"],["9590acd916473f2c8ee27b8c38b1315c86812d74","380081620a7947c89c11153c5513f34019caa923@android.com","cpufreq: Prevent memory leak in cpufreq_stats on hotplug\n\nEnsures that cpufreq_stats_free_table is called before\n__cpufreq_remove_dev on cpu hotplug (which also occurs during\nsuspend on SMP systems) to make sure that sysfs_remove_group\ncan get called before the cpufreq kobj is freed.  Otherwise,\nthe sysfs file structures are leaked.\n\nChange-Id: I87e55277272f5cfad47e9e7c92630e990bb90069\nSigned-off-by: Colin Cross <ccross@android.com>","Colin Cross"],["c44ef11ff5563b23f1b93dcd814b3d994ef05dbc","469a7dfe82496d5a89b11dd78d299ecdbb7f11a7@gmail.com","Fix kernel compression support","snq-"],["9488979f44e937dbcc439758291a8eee223315d5","7f5bb03cf507c861269be561971108be8f37d832@chemlab.org","yaffs2: Import YAFFS2 as of Wed Dec 1 13:51:27 2010 +1300","Steve Kondik"],["39d5843230568d1bafc0054878e80be4d6edd399","60c6d277a8bd81de7fdde19201bf9c58a3df08f4@derhofbauer.at","Forward port Legend files","Alexander Hofbauer"]],"repo":"aleho/htc-kernel-legend","actor":"aleho","ref":"refs/heads/legend-2.6.35","size":19,"head":"39d5843230568d1bafc0054878e80be4d6edd399","actor_gravatar":"d7e15ee0500160118b3cb6c3f35599b9","push_id":31466982}