{"push_id":1296743263,"size":39,"distinct_size":39,"ref":"refs/heads/for-cm","head":"8f28856836e97f3f8e17582a9f59641292674395","before":"b16e46c58d7da95c4300af5faba62b2ab00925d7","commits":[{"sha":"4134b73f8bc36c4de2f6c664a7acea3403e17d0b","author":{"name":"Colin Cross","email":"c3eb3589476a85b6e3c54298f5e4883ee431d748@android.com"},"message":"ARM: sched_clock: update epoch_cyc on resume\n\nMany clocks that are used to provide sched_clock will reset during\nsuspend.  If read_sched_clock returns 0 after suspend, sched_clock will\nappear to jump forward.  This patch resets cd.epoch_cyc to the current\nvalue of read_sched_clock during resume, which causes sched_clock() just\nafter suspend to return the same value as sched_clock() just before\nsuspend.\n\nIn addition, during the window where epoch_ns has been updated before\nsuspend, but epoch_cyc has not been updated after suspend, it is unknown\nwhether the clock has reset or not, and sched_clock() could return a\nbogus value.  Add a suspended flag, and return the pre-suspend epoch_ns\nvalue during this period.\n\nThe new behavior is triggered by calling setup_sched_clock_needs_suspend\ninstead of setup_sched_clock.\n\nChange-Id: Ieb02d180d17c8f3405f0888f4896eb9424d0cdfd\nSigned-off-by: Colin Cross <ccross@android.com>","distinct":true,"url":"https://api.github.com/repos/sigma-1/android_kernel_samsung_n1awifi/commits/4134b73f8bc36c4de2f6c664a7acea3403e17d0b"},{"sha":"a1bfa22082ddf1a2922e62e074f9225d97be0210","author":{"name":"Lianwei Wang","email":"2a68c42e91763605edde1060505920602080ca05@motorola.com"},"message":"cpufreq: interactive: fix race on governor start/stop\n\nThere is race condition when both two cpu do CPUFREQ_GOV_STOP and one cpu\ndo CPUFREQ_GOV_START soon. The sysfs_remove_group is not done yet on one\ncpu, but sysfs_create_group is called on another cpu, which cause governor\nstart failed and then kernel panic in timer callback because the policy and\ncpu mask are all kfree in cpufreq driver.\n\nReplace atomic with mutex to lock the whole START/STOP sequence.\n\nChange-Id: I3762b3d44315ae021b8275aca84f5ea9147cc540\nSigned-off-by: Lianwei Wang <a22439@motorola.com>","distinct":true,"url":"https://api.github.com/repos/sigma-1/android_kernel_samsung_n1awifi/commits/a1bfa22082ddf1a2922e62e074f9225d97be0210"},{"sha":"fd9605034cd6c48fe87aafb42e53b7142e61c451","author":{"name":"Todd Poynor","email":"029db66065441d2248abc6ad98d5a188dfd3826a@google.com"},"message":"power: android-battery: remove ac and usb supplies\n\nShould no longer need to fix up AC/USB online state via these.\n\nChange-Id: I48d2ef0fbefee58cb47eafc11d9a44759920df7a\nSigned-off-by: Todd Poynor <toddpoynor@google.com>","distinct":true,"url":"https://api.github.com/repos/sigma-1/android_kernel_samsung_n1awifi/commits/fd9605034cd6c48fe87aafb42e53b7142e61c451"},{"sha":"ff1165df37a543726729d17b56f4e3b5bcc10adb","author":{"name":"Todd Poynor","email":"029db66065441d2248abc6ad98d5a188dfd3826a@google.com"},"message":"power: android-battery: push uevent whenever charge source changes\n\nEnsure userspace reads an up-to-date value for charging status whenever the\ncharge source is updated.  Avoid races where stale charging state may be\nreflected in userspace until the next battery state poll.\n\nChange-Id: Ia744db48584e9e9abf442710c279af9e3a25c079\nSigned-off-by: Todd Poynor <toddpoynor@google.com>","distinct":true,"url":"https://api.github.com/repos/sigma-1/android_kernel_samsung_n1awifi/commits/ff1165df37a543726729d17b56f4e3b5bcc10adb"},{"sha":"fce22fbe29a11e66c5af38fd78d3f76d6956b5ce","author":{"name":"Jamie Gennis","email":"98df32e8e9382e41624cd4795e4cce268ea52572@google.com"},"message":"sync: fix timeout = 0 wait behavior\n\nChange-Id: I8b9254e92c26d9f44abbc0c77fb44624de947013\nSigned-off-by: Jamie Gennis <jgennis@google.com>","distinct":true,"url":"https://api.github.com/repos/sigma-1/android_kernel_samsung_n1awifi/commits/fce22fbe29a11e66c5af38fd78d3f76d6956b5ce"},{"sha":"8c0364d540b8c14262fed0f541354a84ca59d67c","author":{"name":"Minsung Kim","email":"60511c9840a082917ab2ea9cab833a1447cf5b9f@samsung.com"},"message":"cpufreq: interactive: allow arbitrary speed / delay mappings\n\nAccept a string of delays and speeds at which to apply the delay before\nraising each step above hispeed. For example, \"80000 1300000:200000\n1500000:40000\" means that the delay at or above 1GHz, until 1.3GHz is 80 msecs,\nthe delay until 1.5GHz is 200 msecs and the delay at or above 1.5GHz is 40\nmsecs when hispeed_freq is 1GHz.\n\n[toddpoynor@google.com: add documentation]\nChange-Id: Ifeebede8b1acbdd0a53e5c6916bccbf764dc854f\nSigned-off-by: Minsung Kim <ms925.kim@samsung.com>","distinct":true,"url":"https://api.github.com/repos/sigma-1/android_kernel_samsung_n1awifi/commits/8c0364d540b8c14262fed0f541354a84ca59d67c"},{"sha":"bb09647dbea0069a3dccda4b21dfd09567e3916c","author":{"name":"Lianwei Wang","email":"4a02f7b1d99612ca2e4abd7267530ecf23e3148b@motorola.com"},"message":"cpufreq: interactive: add io_is_busy interface\n\nPreviously the idle time returned from get_cpu_idle_time_us included the\niowait time. So the iowait time was always calculated as idle time.\n\nBut now the idle time returned from get_cpu_idle_time_us does not include\nthe iowait time anymore because of below commit which cause the iowait time\nalways calculated as busy time:\n    6beea0c nohz: Fix update_ts_time_stat idle accounting\n\nAdd the io_is_busy interface, as does the ondemand governor, and let the user\nconfigure the iowait time as busy or idle through the io_is_busy sysfs\ninterface.\n\nBy default, io_is_busy is disabled.\n\n[toddpoynor@google.com: minor updates]\nChange-Id: If7d70ff864c43bc9c8d7fd7cfc66f930d339f9b4\nSigned-off-by: Lianwei Wang <lian-wei.wang@motorola.com>\nSigned-off-by: Todd Poynor <toddpoynor@google.com>","distinct":true,"url":"https://api.github.com/repos/sigma-1/android_kernel_samsung_n1awifi/commits/bb09647dbea0069a3dccda4b21dfd09567e3916c"},{"sha":"8d77b252abc7706ebd2dc8bf8c1301adaba23cc5","author":{"name":"Todd Poynor","email":"029db66065441d2248abc6ad98d5a188dfd3826a@google.com"},"message":"cpufreq: interactive: fix crash on error paths in get_tokenized_data\n\nUse separate variable for error code, free proper pointer.\n\nChange-Id: Ia83cccb195997789ac6afbf5b8761f7b278196d6\nReported-by: Arve Hjønnevåg <arve@android.com>\nSigned-off-by: Todd Poynor <toddpoynor@google.com>","distinct":true,"url":"https://api.github.com/repos/sigma-1/android_kernel_samsung_n1awifi/commits/8d77b252abc7706ebd2dc8bf8c1301adaba23cc5"},{"sha":"f84e48fff58c5cbce9ed0a35ef75889511ff6e42","author":{"name":"Todd Poynor","email":"029db66065441d2248abc6ad98d5a188dfd3826a@google.com"},"message":"cpufreq: interactive: base above_hispeed_delay on target freq, not current\n\nTime to wait should be based on the intended target speed, not the\nactual speed (which may be held high by another CPU).\n\nChange-Id: Ifc5bb55d06adddb9a02af90af05398a78f282272\nReported-by: Arve Hjønnevåg <arve@android.com>\nSigned-off-by: Todd Poynor <toddpoynor@google.com>","distinct":true,"url":"https://api.github.com/repos/sigma-1/android_kernel_samsung_n1awifi/commits/f84e48fff58c5cbce9ed0a35ef75889511ff6e42"},{"sha":"06c8b3086b045937dad7f07017969088857edcb0","author":{"name":"Lars-Peter Clausen","email":"7f698333860e9f21dcc513102ebee3bcaf8d683e@metafoo.de"},"message":"ASoC: dma-sh7760: Fix compile error\n\ncommit 417a1178f1bf3cdc606376b3ded3a22489fbb3eb upstream.\n\nThe dma-sh7760 currently fails with the following compile error:\n\tsound/soc/sh/dma-sh7760.c:346:2: error: unknown field 'pcm_ops' specified in initializer\n\tsound/soc/sh/dma-sh7760.c:346:2: warning: initialization from incompatible pointer type\n\tsound/soc/sh/dma-sh7760.c:347:2: error: unknown field 'pcm_new' specified in initializer\n\tsound/soc/sh/dma-sh7760.c:347:2: warning: initialization makes integer from pointer without a cast\n\tsound/soc/sh/dma-sh7760.c:348:2: error: unknown field 'pcm_free' specified in initializer\n\tsound/soc/sh/dma-sh7760.c:348:2: warning: initialization from incompatible pointer type\n\tsound/soc/sh/dma-sh7760.c: In function 'sh7760_soc_platform_probe':\n\tsound/soc/sh/dma-sh7760.c:353:2: warning: passing argument 2 of 'snd_soc_register_platform' from incompatible pointer type\n\tinclude/sound/soc.h:368:5: note: expected 'struct snd_soc_platform_driver *' but argument is of type 'struct snd_soc_platform *'\n\nThis is due the misnaming of the snd_soc_platform_driver type name and 'ops'\nfield. The issue was introduced in commit f0fba2a(\"ASoC: multi-component - ASoC\nMulti-Component Support\").\n\nSigned-off-by: Lars-Peter Clausen <lars@metafoo.de>\nSigned-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/sigma-1/android_kernel_samsung_n1awifi/commits/06c8b3086b045937dad7f07017969088857edcb0"},{"sha":"93a8146e85589a91339e3d3e140e24155e41fb76","author":{"name":"Lars-Peter Clausen","email":"7f698333860e9f21dcc513102ebee3bcaf8d683e@metafoo.de"},"message":"regmap: cache Fix regcache-rbtree sync\n\ncommit 8abac3ba51b5525354e9b2ec0eed1c9e95c905d9 upstream.\n\nThe last register block, which falls into the specified range, is not handled\ncorrectly. The formula which calculates the number of register which should be\nsynced is inverse (and off by one). E.g. if all registers in that block should\nbe synced only one is synced, and if only one should be synced all (but one) are\nsynced. To calculate the number of registers that need to be synced we need to\nsubtract the number of the first register in the block from the max register\nnumber and add one. This patch updates the code accordingly.\n\nThe issue was introduced in commit ac8d91c (\"regmap: Supply ranges to the sync\noperations\").\n\nSigned-off-by: Lars-Peter Clausen <lars@metafoo.de>\nSigned-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/sigma-1/android_kernel_samsung_n1awifi/commits/93a8146e85589a91339e3d3e140e24155e41fb76"},{"sha":"928845ec4ffefdcc4b38427a410d1ba6c58456a3","author":{"name":"Girish K S","email":"f66f78373758a0f7cea3d96d29d61e302ed975cc@gmail.com"},"message":"spi/s3c64xx: modified error interrupt handling and init\n\ncommit 375981f2e14868be16cafbffd34a4f16a6ee01c6 upstream.\n\nThe status of the interrupt is available in the status register,\nso reading the clear pending register and writing back the same\nvalue will not actually clear the pending interrupts. This patch\nmodifies the interrupt handler to read the status register and\nclear the corresponding pending bit in the clear pending register.\n\nModified the hwInit function to clear all the pending interrupts.\n\nSigned-off-by: Girish K S <ks.giri@samsung.com>\nSigned-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/sigma-1/android_kernel_samsung_n1awifi/commits/928845ec4ffefdcc4b38427a410d1ba6c58456a3"},{"sha":"888e24d4fcc88baea79f6544c924caa01417b6b1","author":{"name":"Anatolij Gustschin","email":"5b619185b5e2c2a99502832285190bc8b7050325@denx.de"},"message":"spi/mpc512x-psc: optionally keep PSC SS asserted across xfer segmensts\n\ncommit 1ad849aee5f53353ed88d9cd3d68a51b03a7d44f upstream.\n\nSome SPI slave devices require asserted chip select signal across\nmultiple transfer segments of an SPI message. Currently the driver\nalways de-asserts the internal SS signal for every single transfer\nsegment of the message and ignores the 'cs_change' flag of the\ntransfer description. Disable the internal chip select (SS) only\nif this is needed and indicated by the 'cs_change' flag.\n\nWithout this change, each partial transfer of a surrounding\nmulti-part SPI transaction might erroneously change the SS\nsignal, which might prevent slaves from answering the request\nthat was sent in a previous transfer segment because the\ntransaction could be considered aborted (SS was de-asserted\nbefore reading the response).\n\nReported-by: Gerhard Sittig <gerhard.sittig@ifm.com>\nSigned-off-by: Anatolij Gustschin <agust@denx.de>\nSigned-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/sigma-1/android_kernel_samsung_n1awifi/commits/888e24d4fcc88baea79f6544c924caa01417b6b1"},{"sha":"52d237423cc45c511e72c4a929265afda0f307e6","author":{"name":"Artem Bityutskiy","email":"41ea5dbf7c14082392bca66bc06c733fa8b2e808@linux.intel.com"},"message":"UBIFS: make space fixup work in the remount case\n\ncommit 67e753ca41782913d805ff4a8a2b0f60b26b7915 upstream.\n\nThe UBIFS space fixup is a useful feature which allows to fixup the \"broken\"\nflash space at the time of the first mount. The \"broken\" space is usually the\nresult of using a \"dumb\" industrial flasher which is not able to skip empty\nNAND pages and just writes all 0xFFs to the empty space, which has grave\nside-effects for UBIFS when UBIFS trise to write useful data to those empty\npages.\n\nThe fix-up feature works roughly like this:\n1. mkfs.ubifs sets the fixup flag in UBIFS superblock when creating the image\n   (see -F option)\n2. when the file-system is mounted for the first time, UBIFS notices the fixup\n   flag and re-writes the entire media atomically, which may take really a lot\n   of time.\n3. UBIFS clears the fixup flag in the superblock.\n\nThis works fine when the file system is mounted R/W for the very first time.\nBut it did not really work in the case when we first mount the file-system R/O,\nand then re-mount R/W. The reason was that we started the fixup procedure too\nlate, which we cannot really do because we have to fixup the space before it\nstarts being used.\n\nSigned-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>\nReported-by: Mark Jackson <mpfj-list@mimc.co.uk>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/sigma-1/android_kernel_samsung_n1awifi/commits/52d237423cc45c511e72c4a929265afda0f307e6"},{"sha":"ff04e908edefda38105f4f40196ec1d54054a88d","author":{"name":"Jan Kara","email":"7bb7087018cc5fef3c041f6f038f586664845dbf@suse.cz"},"message":"reiserfs: Fix warning and inode leak when deleting inode with xattrs\n\ncommit 35e5cbc0af240778e61113286c019837e06aeec6 upstream.\n\nAfter commit 21d8a15a (lookup_one_len: don't accept . and ..) reiserfs\nstarted failing to delete xattrs from inode. This was due to a buggy\ntest for '.' and '..' in fill_with_dentries() which resulted in passing\n'.' and '..' entries to lookup_one_len() in some cases. That returned\nerror and so we failed to iterate over all xattrs of and inode.\n\nFix the test in fill_with_dentries() along the lines of the one in\nlookup_one_len().\n\nReported-by: Pawel Zawora <pzawora@gmail.com>\nSigned-off-by: Jan Kara <jack@suse.cz>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/sigma-1/android_kernel_samsung_n1awifi/commits/ff04e908edefda38105f4f40196ec1d54054a88d"},{"sha":"fcd48a29dd187ebd99b4475152edad1881d46726","author":{"name":"Mengdong Lin","email":"d90c1ec918840faf9cb0df086e27887ad2a1830e@intel.com"},"message":"ALSA: hda - bug fix on return value when getting HDMI ELD info\n\ncommit 2ef5692efad330b67a234e2c49edad38538751e7 upstream.\n\nIn function snd_hdmi_get_eld(), the variable 'ret' should be initialized to 0.\nOtherwise it will be returned uninitialized as non-zero after ELD info is got\nsuccessfully. Thus hdmi_present_sense() will always assume ELD info is invalid\nby mistake, and /proc file system cannot show the proper ELD info.\n\nSigned-off-by: Mengdong Lin <mengdong.lin@intel.com>\nAcked-by: David Henningsson <david.henningsson@canonical.com>\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/sigma-1/android_kernel_samsung_n1awifi/commits/fcd48a29dd187ebd99b4475152edad1881d46726"},{"sha":"5a74e992bb381ef5b54716f48efb089acf24fa13","author":{"name":"Rainer Koenig","email":"55232e53a049b3b30a93b426b1bd7207d4be8d03@ts.fujitsu.com"},"message":"ALSA: hda - Enabling Realtek ALC 671 codec\n\ncommit 1d87caa69c04008e09f5ff47b5e6acb6116febc7 upstream.\n\n* Added the device ID to the modalias list and assinged ALC662 patches\nfor it\n* Added 4 port support for the device ID 0671 in alc662_parse_auto_config\n\nSigned-off-by: Rainer Koenig <Rainer.Koenig@ts.fujitsu.com>\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/sigma-1/android_kernel_samsung_n1awifi/commits/5a74e992bb381ef5b54716f48efb089acf24fa13"},{"sha":"e1efb1181f46e91deb4e35e608831b6b5a3fdaae","author":{"name":"David Henningsson","email":"55b858c3d0ddeb53024f3f979bca66a4eb329d94@canonical.com"},"message":"ALSA: hda - fix typo in proc output\n\ncommit aeb3a97222832e5457c4b72d72235098ce4bfe8d upstream.\n\nRename \"Digitial In\" to \"Digital In\". This function is only used for\nproc output, so should not cause any problems to change.\n\nSigned-off-by: David Henningsson <david.henningsson@canonical.com>\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/sigma-1/android_kernel_samsung_n1awifi/commits/e1efb1181f46e91deb4e35e608831b6b5a3fdaae"},{"sha":"a17c69b80bab09181c6b46c8e6dc03e7c385238a","author":{"name":"Yinghai Lu","email":"a937ac6bd902974249c050ded6c056a9879800aa@kernel.org"},"message":"EISA/PCI: Init EISA early, before PNP\n\ncommit c5fb301ae83bec6892e54984e6ec765c47df8e10 upstream.\n\nMatthew reported kernels fail the pci_eisa probe and are later successful\nwith the virtual_eisa_root_init force probe without slot0.\n\nThe reason for that is: PNP probing is before pci_eisa_init gets called\nas pci_eisa_init is called via pci_driver.\n\npnp 00:0f has 0xc80 - 0xc84 reserved.\n[    9.700409] pnp 00:0f: [io  0x0c80-0x0c84]\n\nso eisa_probe will fail from pci_eisa_init\n\t\t\t\t==>eisa_root_register\n\t\t\t\t\t==>eisa_probe path.\nas force_probe is not set in pci_eisa_root, it will bail early when\nslot0 is not probed and initialized.\n\nTry to use subsys_initcall_sync instead, and will keep following sequence:\n\tpci_subsys_init\n\tpci_eisa_init_early\n\tpnpacpi_init/isapnp_init\n\nAfter this patch EISA can be initialized properly, and PNP overlapping\nresource will not be reserved.\n[   10.104434] system 00:0f: [io  0x0c80-0x0c84] could not be reserved\n\nReported-by: Matthew Whitehead <mwhitehe@redhat.com>\nTested-by: Matthew Whitehead <mwhitehe@redhat.com>\nSigned-off-by: Yinghai Lu <yinghai@kernel.org>\nSigned-off-by: Bjorn Helgaas <bhelgaas@google.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/sigma-1/android_kernel_samsung_n1awifi/commits/a17c69b80bab09181c6b46c8e6dc03e7c385238a"},{"sha":"9f3f984d6a449a3850e6e23d43d7dd67809069ba","author":{"name":"Yinghai Lu","email":"a937ac6bd902974249c050ded6c056a9879800aa@kernel.org"},"message":"EISA/PCI: Fix bus res reference\n\ncommit 2cfda637e29ce9e3df31b59f64516b2e571cc985 upstream.\n\nMatthew found that 3.8.3 is having problems with an old (ancient)\nPCI-to-EISA bridge, the Intel 82375. It worked with the 3.2 kernel.\nHe identified the 82375, but doesn't assign the struct resource *res\npointer inside the struct eisa_root_device, and panics.\n\npci_eisa_init() was using bus->resource[] directly instead of\npci_bus_resource_n().  The bus->resource[] array is a PCI-internal\nimplementation detail, and after commit 45ca9e97 (PCI: add helpers for\nbuilding PCI bus resource lists) and commit 0efd5aab (PCI: add struct\npci_host_bridge_window with CPU/bus address offset), bus->resource[] is not\nused for PCI root buses any more.\n\nThe 82375 is a subtractive-decode PCI device, so handle it the same\nway we handle PCI-PCI bridges in subtractive-decode mode in\npci_read_bridge_bases().\n\n[bhelgaas: changelog]\nReported-by: Matthew Whitehead <mwhitehe@redhat.com>\nTested-by: Matthew Whitehead <mwhitehe@redhat.com>\nSigned-off-by: Yinghai Lu <yinghai@kernel.org>\nSigned-off-by: Bjorn Helgaas <bhelgaas@google.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/sigma-1/android_kernel_samsung_n1awifi/commits/9f3f984d6a449a3850e6e23d43d7dd67809069ba"}]}
{"actor":{"display_login":"sigma-1"}}