{"push_id":601491291,"size":18,"distinct_size":18,"ref":"refs/heads/cm-12.0-test","head":"b95f1a324192e981ed74ec14cfbf07ace89d4ab9","before":"00091e05b75e31c13c16d780677237ad5fee7988","commits":[{"sha":"e48be7eb35757836f42abc57d8fdcf950d1adf5a","author":{"email":"aa248032246d31778cc01f6793bbc94e84637066@gmail.com","name":"Tommy-Geenexus"},"message":"xt_socket: pointers should be initialized with NULL","distinct":true,"url":"https://api.github.com/repos/c0llal0/kernel_xperia_z/commits/e48be7eb35757836f42abc57d8fdcf950d1adf5a"},{"sha":"6c8de90ab7dfcc57b47f8130c25c51ec3a4995dc","author":{"email":"f2c659f01951776204a6c5b902787d9019fbeebd@arndb.de","name":"Arnd Bergmann"},"message":"Turn off -Wmaybe-uninitialized when building with -Os\n\ngcc-4.7 and higher add a lot of false positive warnings about\npotential uses of uninitialized warnings, but only when optimizing\nfor size (-Os). This is the default when building allyesconfig,\nwhich turns on CONFIG_CC_OPTIMIZE_FOR_SIZE.\n\nIn order to avoid getting a lot of patches that initialize such\nvariables and accidentally hide real errors along the way, let's\njust turn off this warning on the respective gcc versions\nwhen building with size optimizations. The -Wmaybe-uninitialized\noption was introduced in the same gcc version (4.7) that is now\ncausing the false positives, so there is no effect on older compilers.\n\nA side effect is that when building with CONFIG_CC_OPTIMIZE_FOR_SIZE,\nwe might now see /fewer/ warnings about possibly uninitialized\nwarnings than with -O2, but that is still much better than seeing\nwarnings known to be bogus.\n\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>\nGit-commit: e74fc973b6e531fef1fce8b101ffff05ecfb774c\nGit-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git\nSigned-off-by: Bryan Huntsman <bryanh@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/c0llal0/kernel_xperia_z/commits/6c8de90ab7dfcc57b47f8130c25c51ec3a4995dc"},{"sha":"6f5f2c28ce38569e9b66235ed5f780de066779db","author":{"email":"aa248032246d31778cc01f6793bbc94e84637066@gmail.com","name":"Tommy-Geenexus"},"message":"tty: remove smux_debug","distinct":true,"url":"https://api.github.com/repos/c0llal0/kernel_xperia_z/commits/6f5f2c28ce38569e9b66235ed5f780de066779db"},{"sha":"56a1bd3aab4741ec8d6c8b7d47ceacc6a5cf696c","author":{"email":"75f5229649ddd37dbeee396697fbac9322add040@hotmail.com","name":"daeiron"},"message":"Disable CRC check mmc/core\n\nChange-Id: I1d3e67205f0adf6fd31775db005d9264858075a5","distinct":true,"url":"https://api.github.com/repos/c0llal0/kernel_xperia_z/commits/56a1bd3aab4741ec8d6c8b7d47ceacc6a5cf696c"},{"sha":"b046d4f5f688dc07afc13b59473cf17825b08f65","author":{"email":"aa248032246d31778cc01f6793bbc94e84637066@gmail.com","name":"Tommy-Geenexus"},"message":"msm: remove clock_debug\n\nConflicts:\n\tarch/arm/mach-msm/Makefile","distinct":true,"url":"https://api.github.com/repos/c0llal0/kernel_xperia_z/commits/b046d4f5f688dc07afc13b59473cf17825b08f65"},{"sha":"431f443722fa1f7b18038d67d35d153ffcf0e30c","author":{"email":"75f5229649ddd37dbeee396697fbac9322add040@hotmail.com","name":"daeiron"},"message":"Remove dma test","distinct":true,"url":"https://api.github.com/repos/c0llal0/kernel_xperia_z/commits/431f443722fa1f7b18038d67d35d153ffcf0e30c"},{"sha":"8d5214c1aa927339230b3aa8af7bbf63db337f6c","author":{"email":"75f5229649ddd37dbeee396697fbac9322add040@hotmail.com","name":"daeiron"},"message":"Remove some more debugging","distinct":true,"url":"https://api.github.com/repos/c0llal0/kernel_xperia_z/commits/8d5214c1aa927339230b3aa8af7bbf63db337f6c"},{"sha":"086f4e2607ee3eda435dc89bd55d962b9bb6b514","author":{"email":"75f5229649ddd37dbeee396697fbac9322add040@hotmail.com","name":"daeiron"},"message":"Bye block tests","distinct":true,"url":"https://api.github.com/repos/c0llal0/kernel_xperia_z/commits/086f4e2607ee3eda435dc89bd55d962b9bb6b514"},{"sha":"e85e6e8d4a625eafdeaa232c2e1f0f341959977f","author":{"email":"672c7f5d7c31e5aba75fbe0bc303fff4514dcd5f@gmail.com","name":"morfic"},"message":"Mako (absolute) Voltage control.\n\nThis started out as just including the existing work of someone else.\nBut that was so obfuscated and needlessly moved in sysfs, i turned it into the type control\nwe have on NP, meaning same sysfs location and output formatting.\nSince the various kernels range from no preUV to different levels of UV it is best to encourage the user\nto think in absolute voltages.\n\"I can UV -150 on kernel X! Really? Odd, i can only UV kernel Y -50mV!\"\nKernel X has no preUV, kernel Y has 100mV preUV, so they both run the same.\nThis is needlessly confusing to users.\n\nTalking in absolutes, users will get a better understanding of \"what the other guy's\" device is capable of.\nSticking to a common sysfs location and to the common absolute voltage is thus the right thing to do.\n\nThis seems to work now as it should.\n\nThis is heavily based on coolbho3k's NP patch. from Paul's mess we might have a few function names, but not the contents.\nThis is not his, if he claims otherwise, he can go fuck himself.\n\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>\n\nUndervolt: clean it up, make it elegant and remove the constrain of fixed set of NUM_FREQS - its not dynamic based on the number of freqs used for scaling via an external function.\n\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>\n\nUndervolt: few minor changes, mostly for clarity.\n\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>\n\nUndervolt: add checks to disallow too extreme voltages, min and max.\n\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>\n\nmsm: fix indendation and improve the routines.\n\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/c0llal0/kernel_xperia_z/commits/e85e6e8d4a625eafdeaa232c2e1f0f341959977f"},{"sha":"f90c9ce986ed58bd49d5507f6b40c5c9ae7aa88a","author":{"email":"cb3904095a5bc20edc93ba3dfa3e7d27d981b654@intel.com","name":"Shaohua Li"},"message":"block: fiops ioscheduler core\n\nFIOPS (Fair IOPS) ioscheduler is IOPS based ioscheduler, so only targets\nfor drive without I/O seek. It's quite similar like CFQ, but the dispatch\ndecision is made according to IOPS instead of slice.\n\nThe algorithm is simple. Drive has a service tree, and each task lives in\nthe tree. The key into the tree is called vios (virtual I/O). Every request\nhas vios, which is calculated according to its ioprio, request size and so\non. Task's vios is the sum of vios of all requests it dispatches. FIOPS\nalways selects task with minimum vios in the service tree and let the task\ndispatch request. The dispatched request's vios is then added to the task's\nvios and the task is repositioned in the sevice tree.\n\nUnlike CFQ, FIOPS doesn't have separate sync/async queues, because with I/O\nless writeback, usually a task can only dispatch either sync or async requests.\nBias read or write request can still be done with read/write scale.\n\nOne issue is if workload iodepth is lower than drive queue_depth, IOPS\nshare of a task might not be strictly according to its priority, request\nsize and so on. In this case, the drive is in idle actually. Solving the\nproblem need make drive idle, so impact performance. I believe CFQ isn't\ncompletely fair between tasks in such case too.\n\nSigned-off-by: Shaohua Li <shaohua.li@intel.com>\n\nConflicts:\n\tblock/Kconfig.iosched\n\tblock/Makefile","distinct":true,"url":"https://api.github.com/repos/c0llal0/kernel_xperia_z/commits/f90c9ce986ed58bd49d5507f6b40c5c9ae7aa88a"},{"sha":"6a112edb342ac040396d6aea7ce2b8788d93f16d","author":{"email":"25c6e130555f1e8cd4f8c64fd573c9993e5af6a5@googlemail.com","name":"c0llal0"},"message":"block: fix fiops ioschedular merge derp","distinct":true,"url":"https://api.github.com/repos/c0llal0/kernel_xperia_z/commits/6a112edb342ac040396d6aea7ce2b8788d93f16d"},{"sha":"8954bbf5ae41b000a0f8e71862a57d416e8a2ac4","author":{"email":"cb3904095a5bc20edc93ba3dfa3e7d27d981b654@intel.com","name":"Shaohua Li"},"message":"block: fiops read/write request scale\n\nread/write speed of Flash based storage usually is different. For example,\nin my SSD maxium thoughput of read is about 3 times faster than that of\nwrite. Add a scale to differenate read and write. Also add a tunable, so\nuser can assign different scale for read and write.\n\nBy default, the scale is 1:1, which means the scale is a noop.\n\nSigned-off-by: Shaohua Li <shaohua.li@intel.com>","distinct":true,"url":"https://api.github.com/repos/c0llal0/kernel_xperia_z/commits/8954bbf5ae41b000a0f8e71862a57d416e8a2ac4"},{"sha":"856409af201acaa94770eaf0251b30034469d592","author":{"email":"cb3904095a5bc20edc93ba3dfa3e7d27d981b654@intel.com","name":"Shaohua Li"},"message":"block: fiops sync/async scale\n\nCFQ gives 2.5 times more share to sync workload. This matches CFQ.\n\nNote this is different with the read/write scale. We have 3 types of\nrequests:\n1. read\n2. sync write\n3. write\nCFQ doesn't differentitate type 1 and 2, but request cost of 1 and 2\nare usually different for flash based storage. So we have both sync/async\nand read/write scale here.\n\nSigned-off-by: Shaohua Li <shaohua.li@intel.com>","distinct":true,"url":"https://api.github.com/repos/c0llal0/kernel_xperia_z/commits/856409af201acaa94770eaf0251b30034469d592"},{"sha":"fc3ef4387baa827db59b15385bf7421040fc174e","author":{"email":"cb3904095a5bc20edc93ba3dfa3e7d27d981b654@intel.com","name":"Shaohua Li"},"message":"block: fiops add ioprio support\n\nAdd CFQ-like ioprio support. Priority A will get 20% more share than priority\nA+1, which matches CFQ.\n\nSigned-off-by: Shaohua Li <shaohua.li@intel.com>","distinct":true,"url":"https://api.github.com/repos/c0llal0/kernel_xperia_z/commits/fc3ef4387baa827db59b15385bf7421040fc174e"},{"sha":"74730bd1f15f7e9424840fce1c26ca0a1fce16d1","author":{"email":"cb3904095a5bc20edc93ba3dfa3e7d27d981b654@intel.com","name":"Shaohua Li"},"message":"block: fiops preserve vios key for deep queue depth workload\n\nIf the task has running request, even it's added into service tree newly,\nwe preserve its vios key, so it will not lost its share. This should work\nfor task driving big queue depth. For single depth task, there is no approach\nto preserve its vios key.\n\nSigned-off-by: Shaohua Li <shaohua.li@intel.com>","distinct":true,"url":"https://api.github.com/repos/c0llal0/kernel_xperia_z/commits/74730bd1f15f7e9424840fce1c26ca0a1fce16d1"},{"sha":"9dec0729c551c8abac3b227972a0fb45a049b49e","author":{"email":"cb3904095a5bc20edc93ba3dfa3e7d27d981b654@intel.com","name":"Shaohua Li"},"message":"block: fiops bias sync workload\n\nIf there are async requests running, delay async workload. Otherwise\nasync workload (usually very deep iodepth) will use all queue iodepth\nand later sync requests will get long delayed. The idea is from CFQ.\n\nSigned-off-by: Shaohua Li <shaohua.li@intel.com>","distinct":true,"url":"https://api.github.com/repos/c0llal0/kernel_xperia_z/commits/9dec0729c551c8abac3b227972a0fb45a049b49e"},{"sha":"4868261626138fc95129b2b7f78ad4fea97b027d","author":{"email":"cb3904095a5bc20edc93ba3dfa3e7d27d981b654@intel.com","name":"Shaohua Li"},"message":"block: fiops add some trace information\n\nAdd some trace information, which is helpful when I do debugging.\n\nSigned-off-by: Shaohua Li <shaohua.li@intel.com>","distinct":true,"url":"https://api.github.com/repos/c0llal0/kernel_xperia_z/commits/4868261626138fc95129b2b7f78ad4fea97b027d"},{"sha":"b95f1a324192e981ed74ec14cfbf07ace89d4ab9","author":{"email":"c208d1ecece4e5ef2e4fb72f0546c69cdce89063@gmail.com","name":"faux123"},"message":"cpufreq: overall_stats: add overall stats for all available cores\n\nthis is much more accurate stats tracking than just displaying core 0's\nstats from most other kernels\n\nSigned-off-by: faux123 <reioux@gmail.com>\n\noverall_stats: make dual/quad core stats configurable via meunconfig\n\nSigned-off-by: faux123 <reioux@gmail.com>\n\noverall_stats: forward port to kernel 3.4+\n\nby replacing deprecated functions with native add/sub for 64bit data types\n\nChange-Id: I1e17d626bf59b3c0822c9f1088093f848fd2649c\nSigned-off-by: faux123 <reioux@gmail.com>","distinct":true,"url":"https://api.github.com/repos/c0llal0/kernel_xperia_z/commits/b95f1a324192e981ed74ec14cfbf07ace89d4ab9"}]}