{"push_id":802153153,"size":58,"distinct_size":58,"ref":"refs/heads/chromeos-3.8","head":"9da5a0b11f0f11921ac66ae283a53e7c7c6f8722","before":"c7bff7c849ea58f37c8e308b6238e38c3d0df497","commits":[{"sha":"5b5d27f04e378890cc7c188d8a03416d5aec5200","author":{"email":"4596b3305151c7ee743192a95d394341e3d3b644@suse.de","name":"Takashi Iwai"},"message":"UPSTREAM: ALSA: seq: Use atomic ops for autoload refcount\n\n... just to robustify for races.\n\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\n(cherry picked from commit 54841a06c54eb55918948c12ab9b5f02cacb6ab3)\nSigned-off-by: Adam Goode <agoode@chromium.org>\n\nBUG=chromium:499817\nTEST=Build and boot\n\nChange-Id: If30a694294bf9663040b807200d82982a572ac7e\nReviewed-on: https://chromium-review.googlesource.com/277490\nReviewed-by: Dylan Reid <dgreid@chromium.org>\nCommit-Queue: Adam Goode <agoode@chromium.org>\nTested-by: Adam Goode <agoode@chromium.org>","distinct":true,"url":"https://api.github.com/repos/singulared/chromebook-kernel/commits/5b5d27f04e378890cc7c188d8a03416d5aec5200"},{"sha":"d2bed66bdaafd05d1db475370d2e94e6ade3a23c","author":{"email":"4596b3305151c7ee743192a95d394341e3d3b644@suse.de","name":"Takashi Iwai"},"message":"UPSTREAM: ALSA: seq: bind seq driver automatically\n\nCurrently the sequencer module binding is performed independently from\nthe card module itself.  The reason behind it is to keep the sequencer\nstuff optional and allow the system running without it (e.g. for using\nPCM or rawmidi only).  This works in most cases, but a remaining\nproblem is that the binding isn't done automatically when a new driver\nmodule is probed.  Typically this becomes visible when a hotplug\ndriver like usb audio is used.\n\nThis patch tries to address this and other potential issues.  First,\nthe seq-binder (seq_device.c) tries to load a missing driver module at\ncreating a new device object.  This is done asynchronously in a workq\nfor avoiding the deadlock (modprobe call in module init path).\n\nThis action, however, should be enabled only when the sequencer stuff\nwas already initialized, i.e. snd-seq module was already loaded.  For\nthat, a new function, snd_seq_autoload_init() is introduced here; this\nclears the blocking of autoloading, and also tries to load all pending\ndriver modules.\n\nReported-by: Adam Goode <agoode@chromium.org>\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\n\n(cherry picked from commit 68ab61084de3220e2fb0a698c890ba91decddc85)\n\nBUG=chromium:499817\nTEST=Boot with no MIDI devices attached. Go to http://webaudiodemos.appspot.com/midi-synth/index.html and connect a device. Verify that it appears in the MIDI_IN menu on the page.\n\nChange-Id: Ia2d44461cab9682332053d71f96f03c75ce3ccbf\nReviewed-on: https://chromium-review.googlesource.com/277491\nReviewed-by: Dylan Reid <dgreid@chromium.org>\nCommit-Queue: Adam Goode <agoode@chromium.org>\nTested-by: Adam Goode <agoode@chromium.org>","distinct":true,"url":"https://api.github.com/repos/singulared/chromebook-kernel/commits/d2bed66bdaafd05d1db475370d2e94e6ade3a23c"},{"sha":"61d4dc150714cdfda0aa7c930f09751dbbc362a1","author":{"email":"4596b3305151c7ee743192a95d394341e3d3b644@suse.de","name":"Takashi Iwai"},"message":"UPSTREAM: Subject: ALSA: seq: Remove autoload locks in driver registration\n\nSince we're calling request_module() asynchronously now, we can get\nrid of the autoload lock in snd_seq_device_register_driver(), as well\nas in the snd-seq driver registration itself.  This enables the\nautomatic loading of dependent sequencer modules, such as\nsnd-seq-virmidi from snd-emu10k1-synth.\n\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\n\n(cherry picked from commit d5129f33a0d155d69cb0652cfc87bbc4d132ca17)\n\nBUG=chromium:499817\nTEST=build and boot\n\nChange-Id: I595569ea9c2349660f8007b78a24b1cddda22694\nReviewed-on: https://chromium-review.googlesource.com/277492\nReviewed-by: Dylan Reid <dgreid@chromium.org>\nCommit-Queue: Adam Goode <agoode@chromium.org>\nTested-by: Adam Goode <agoode@chromium.org>","distinct":true,"url":"https://api.github.com/repos/singulared/chromebook-kernel/commits/61d4dc150714cdfda0aa7c930f09751dbbc362a1"},{"sha":"a9a45bab8fb4f5e3bfcd32e67fe8c64f27b1ec6e","author":{"email":"7b3b0c46207f6ad0aa76306ba4a81872bd45902a@google.com","name":"Yao-Wen Mao"},"message":"UPSTREAM: ALSA: usb-audio: add dB range mapping for some devices\n\nAdd the correct dB ranges of Bose Companion 5 and Drangonfly DAC 1.2.\n\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\n(cherry picked from commit 2d1cb7f658fb9c3ba8f9dab8aca297d4dfdec835)\nSigned-off-by: Yao-Wen Mao <yaowen@google.com>\n\nBUG=chromium:309459\nTEST=Connect with Bose Companion 5 and use amixer to verify that\nthe volume range is from -50.06dB to -0.06dB.\n\nChange-Id: I0bd0b5665d0d7598724f45e13fa9dda564e33021\nReviewed-on: https://chromium-review.googlesource.com/290486\nReviewed-by: Dylan Reid <dgreid@chromium.org>\nCommit-Queue: Yao-Wen Mao <yaowen@google.com>\nTested-by: Yao-Wen Mao <yaowen@google.com>","distinct":true,"url":"https://api.github.com/repos/singulared/chromebook-kernel/commits/a9a45bab8fb4f5e3bfcd32e67fe8c64f27b1ec6e"},{"sha":"05a21e55cec43b243621edfdcae6843d81c88b20","author":{"email":"8b9c60c177136f4289bffc27dc182e6e6ad5798f@marvell.com","name":"Xinming Hu"},"message":"UPSTREAM: mwifiex: using right aid value for tdls action frame\n\nVariable pos is u8 here, so memcpy is needed to store u16 aid.\nAt the same time, aid should be platform independent, upper layer\nutility(wpa_supplicant,etc.,) parse it as le16, so keep it le16\nhere.\n\nSigned-off-by: Xinming Hu <huxm@marvell.com>\nSigned-off-by: Amitkumar Karwar <akarwar@marvell.com>\nSigned-off-by: Kalle Valo <kvalo@codeaurora.org>\n\nBUG=chrome-os-partner:40462\nTEST=network_WiFi_TDLSPing test consistently passed with\nthis fix.\n\nChange-Id: Iaf08b5b0e83fb71f1412d8b88be8bc092d159093\nSigned-off-by: Amitkumar Karwar <akarwar@marvell.com>\nReviewed-on: https://chromium-review.googlesource.com/291094\nReviewed-by: Paul Stewart <pstew@chromium.org>\nReviewed-by: Sameer Nanda <snanda@chromium.org>","distinct":true,"url":"https://api.github.com/repos/singulared/chromebook-kernel/commits/05a21e55cec43b243621edfdcae6843d81c88b20"},{"sha":"3f6c3222af8132cb7b38537d30e73d0c1e56a671","author":{"email":"fb53b2ddb8d141e0cb39d7c67c2f81b6bc2eb0f7@gmail.com","name":"David Herrmann"},"message":"UPSTREAM: HID: input: fix confusion on conflicting mappings\n\nOn an PC-101/103/104 keyboard (American layout) the 'Enter' key and its\nneighbours look like this:\n\n           +---+ +---+ +-------+\n           | 1 | | 2 | |   5   |\n           +---+ +---+ +-------+\n             +---+ +-----------+\n             | 3 | |     4     |\n             +---+ +-----------+\n\nOn a PC-102/105 keyboard (European layout) it looks like this:\n\n           +---+ +---+ +-------+\n           | 1 | | 2 | |       |\n           +---+ +---+ +-+  4  |\n             +---+ +---+ |     |\n             | 3 | | 5 | |     |\n             +---+ +---+ +-----+\n\n(Note that the number of keys is the same, but key '5' is moved down and\n the shape of key '4' is changed. Keys '1' to '3' are exactly the same.)\n\nThe keys 1-4 report the same scan-code in HID in both layouts, even though\nthe keysym they produce is usually different depending on the XKB-keymap\nused by user-space.\nHowever, key '5' (US 'backslash'/'pipe') reports 0x31 for the upper layout\nand 0x32 for the lower layout, as defined by the HID spec. This is highly\nconfusing as the linux-input API uses a single keycode for both.\n\nSo far, this was never a problem as there never has been a keyboard with\nboth of those keys present at the same time. It would have to look\nsomething like this:\n\n           +---+ +---+ +-------+\n           | 1 | | 2 | |  x31  |\n           +---+ +---+ +-------+\n             +---+ +---+ +-----+\n             | 3 | |x32| |  4  |\n             +---+ +---+ +-----+\n\nHID can represent such a keyboard, but the linux-input API cannot.\nFurthermore, any user-space mapping would be confused by this and,\nluckily, no-one ever produced such hardware.\n\nNow, the HID input layer fixed this mess by mapping both 0x31 and 0x32 to\nthe same keycode (KEY_BACKSLASH==0x2b). As only one of both physical keys\nis present on a hardware, this works just fine.\n\nLets introduce hardware-vendors into this:\n------------------------------------------\n\nUnfortunately, it seems way to expensive to produce a different device for\nAmerican and European layouts. Therefore, hardware-vendors put both keys,\n(0x31 and 0x32) on the same keyboard, but only one of them is hooked up\nto the physical button, the other one is 'dead'.\nThis means, they can use the same hardware, with a different button-layout\nand automatically produce the correct HID events for American *and*\nEuropean layouts. This is unproblematic for normal keyboards, as the\n'dead' key will never report any KEY-DOWN events. But RollOver keyboards\nsend the whole matrix on each key-event, allowing n-key roll-over mode.\nThis means, we get a 0x31 and 0x32 event on each key-press. One of them\nwill always be 0, the other reports the real state. As we map both to the\nsame keycode, we will get spurious key-events, even though the real\nkey-state never changed.\n\nThe easiest way would be to blacklist 'dead' keys and never handle those.\nWe could simply read the 'country' tag of USB devices and blacklist either\nkey according to the layout. But... hardware vendors... want the same\ndevice for all countries and thus many of them set 'country' to 0 for all\ndevices. Meh..\n\nSo we have to deal with this properly. As we cannot know which of the keys\nis 'dead', we either need a heuristic and track those keys, or we simply\nmake use of our value-tracking for HID fields. We simply ignore HID events\nfor absolute data if the data didn't change. As HID tracks events on the\nHID level, we haven't done the keycode translation, yet. Therefore, the\n'dead' key is tracked independently of the real key, therefore, any events\non it will be ignored.\n\nThis patch simply discards any HID events for absolute data if it didn't\nchange compared to the last report. We need to ignore relative and\nbuffered-byte reports for obvious reasons. But those cannot be affected by\nthis bug, so we're fine.\n\nPreferably, we'd do this filtering on the HID-core level. But this might\nbreak a lot of custom drivers, if they do not follow the HID specs.\nTherefore, we do this late in hid-input just before we inject it into the\ninput layer (which does the exact same filtering, but on the keycode\nlevel).\n\nIf this turns out to break some devices, we might have to limit filtering\nto EV_KEY events. But lets try to do the Right Thing first, and properly\nfilter any absolute data that didn't change.\n\nThis patch is tagged for 'stable' as it fixes a lot of n-key RollOver\nhardware. We might wanna wait with backporting for a while, before we know\nit doesn't break anything else, though.\n\nCc: <stable@vger.kernel.org>\nReported-by: Adam Goode <adam@spicenitz.org>\nReported-by: Fredrik Hallenberg <megahallon@gmail.com>\nTested-by: Fredrik Hallenberg <megahallon@gmail.com>\nSigned-off-by: David Herrmann <dh.herrmann@gmail.com>\nSigned-off-by: Jiri Kosina <jkosina@suse.cz>\n(cherry picked from commit 6ce901eb61aa30ba8565c62049ee80c90728ef14)\nSigned-off-by: Adam Goode <agoode@chromium.org>\n\nBUG=chromium:476215\nTEST=Test that backslash \"\\\" key repeats in N-key rollover mode\n\nReviewed-on: https://chromium-review.googlesource.com/291140\nReviewed-by: Dylan Reid <dgreid@chromium.org>\nCommit-Queue: Adam Goode <agoode@chromium.org>\nTested-by: Adam Goode <agoode@chromium.org>\n\n(cherry picked from commit 409be6946f6a84bfe0a61ce47c8d721f4df095b3)\n\nChange-Id: Ie8dd87bf450b511e770bb7f237772bc26945344c\nReviewed-on: https://chromium-review.googlesource.com/291500\nCommit-Ready: Adam Goode <agoode@chromium.org>\nTested-by: Adam Goode <agoode@chromium.org>\nReviewed-by: Dylan Reid <dgreid@chromium.org>","distinct":true,"url":"https://api.github.com/repos/singulared/chromebook-kernel/commits/3f6c3222af8132cb7b38537d30e73d0c1e56a671"},{"sha":"88960eb04c07eb94c0b558a1d0a70aad06b120d5","author":{"email":"5259333ce42e3ace6a73988cec7115ed9d3a661a@chromium.org","name":"Shawn Nematbakhsh"},"message":"CHROMIUM: mfd: lpc_ich: Ignore ACPI GPIO resource conflict for Stout\n\nStout firmware reserves the IO region for ACPI, but never access it.\n\nBUG=chromium:516371\nTEST=Manual on Stout. Verify that gpiochip is successfully probed.\n\nChange-Id: I9067397eb9999b56abf9611da384c64d63ff89aa\nSigned-off-by: Shawn Nematbakhsh <shawnn@chromium.org>\nReviewed-on: https://chromium-review.googlesource.com/290430\nReviewed-by: Grant Grundler <grundler@chromium.org>\nReviewed-by: Sameer Nanda <snanda@chromium.org>","distinct":true,"url":"https://api.github.com/repos/singulared/chromebook-kernel/commits/88960eb04c07eb94c0b558a1d0a70aad06b120d5"},{"sha":"6401c2a7bdfa782f51ec45447ed7a73b3e8a6be7","author":{"email":"ed58f755cc8caaf10c3e8c731a8b86fb8f13d6cb@suse.cz","name":"Jiri Kosina"},"message":"UPSTREAM: HID: fixup the conflicting keyboard mappings quirk\n\nThe ignore check that got added in 6ce901eb61 (\"HID: input: fix confusion\non conflicting mappings\") needs to properly check for VARIABLE reports\nas well (ARRAY reports should be ignored), otherwise legitimate keyboards\nmight break.\n\nCc: <stable@vger.kernel.org>\nFixes: 6ce901eb61 (\"HID: input: fix confusion on conflicting mappings\")\nReported-by: Fredrik Hallenberg <megahallon@gmail.com>\nReported-by: David Herrmann <dh.herrmann@gmail.com>\nSigned-off-by: Jiri Kosina <jkosina@suse.cz>\n(cherry picked from commit 8e7b341037db1835ee6eea64663013cbfcf33575)\nSigned-off-by: Adam Goode <agoode@chromium.org>\n\nBUG=chromium:476215\nTEST=Test that backslash \"\\\" key repeats in N-key rollover mode\n\nReviewed-on: https://chromium-review.googlesource.com/291141\nReviewed-by: Dylan Reid <dgreid@chromium.org>\nCommit-Queue: Adam Goode <agoode@chromium.org>\nTested-by: Adam Goode <agoode@chromium.org>\n\n(cherry picked from commit c45d0f2ee47e085724464fa4d1ea29fa3b31a002)\n\nChange-Id: Iaf4d0c96b36bb48138aa83e2784d1add17760493\nReviewed-on: https://chromium-review.googlesource.com/291501\nCommit-Ready: Adam Goode <agoode@chromium.org>\nTested-by: Adam Goode <agoode@chromium.org>\nReviewed-by: Dylan Reid <dgreid@chromium.org>","distinct":true,"url":"https://api.github.com/repos/singulared/chromebook-kernel/commits/6401c2a7bdfa782f51ec45447ed7a73b3e8a6be7"},{"sha":"c4f107cdc9368a52e062b39b2b26988ea31bc373","author":{"email":"bff32994ff0f8d048f262a8388145a71b6071bfe@intel.com","name":"Johannes Berg"},"message":"CHROMIUM: iwl7000: update to Core11 release\n\nUpdate the iwl7000 driver to the Core11 release.\n\nThis also changes our release model slightly - the code now has\nmore ifdefs on the CFG80211_VERSION and the KERNEL_VERSION so\nthat the same code can be used against multiple versions.\n\nBUG=N/A\nTEST=AVL tests\n\nChange-Id: Iec640580610118dce1b3307407302512ca31a820\nSigned-off-by: Johannes Berg <johannes.berg@intel.com>\nReviewed-on: https://chromium-review.googlesource.com/282776\nReviewed-by: Sameer Nanda <snanda@chromium.org>","distinct":true,"url":"https://api.github.com/repos/singulared/chromebook-kernel/commits/c4f107cdc9368a52e062b39b2b26988ea31bc373"},{"sha":"7a35e06bd89b7e330f4f4d2394db02a03889669e","author":{"email":"5004afe206914bdd0a6fc6438682f9b308a36be6@chromium.org","name":"Luigi Semenzato"},"message":"CHROMIUM: tpm: issue TPM_Savestate proactively to prevent suspend delays\n\n(This patch has no effect unless the module parameter\ntpm.tpm_early_savestate is set to 1.)\n\nSome TPM models can throttle the TPM_Savestate command under certain\nconditions, to prevent wear.  This results in suspend-time increases\nwhich, if ignored, may hide other regressions during automated tests.\nIt can also interfere with the suspend and make it fail.\n\nThis problem is made more acute by the over-throttling behavior\nof a subset of those models (which seems to be an error).  In\nthose models the throttling can be seen even when TPM_Savestate\ncommands are issued far apart from each other.\n\nThe workaround suggested in the bug discussion is to issue a TPM_Savestate\ncommand within some time interval after a command which may change the\nvolatile state of the TPM.  A TPM_Savestate following such command\nrequires the TPM to actually write data to the nvram, which\nmay trigger the throttling.  (If the TPM state has not changed\nsince the last TPM_Savestate, the TPM doesn't need to save it\nagain.)\n\nWe would also like to avoid issuing unnecessary savestate commands.\nIf NO commands are issued following the last TPM_Savestate, it\nshould be OK in general to skip the savestate at suspend.\nUnfortunately at this time we rely on this command to help decrement\nthe dictionary attack counter on some systems, so we leave this\nbehavior configurable via a module parameter.\n\nBUG=chrome-os-partner:26289\nTEST=boot, suspend, resume\nSigned-off-by: Luigi Semenzato <semenzato@chromium.org>\n\nChange-Id: Id062df884d7f37d017041f68af75dd03c12a0b26\nReviewed-on: https://chromium-review.googlesource.com/277726\nReviewed-by: Derek Basehore <dbasehore@chromium.org>\nCommit-Queue: Luigi Semenzato <semenzato@chromium.org>\nTested-by: Luigi Semenzato <semenzato@chromium.org>","distinct":true,"url":"https://api.github.com/repos/singulared/chromebook-kernel/commits/7a35e06bd89b7e330f4f4d2394db02a03889669e"},{"sha":"b9b0e5dd2b3a50025eb48d225c6e281f7b4fbf24","author":{"email":"bff32994ff0f8d048f262a8388145a71b6071bfe@intel.com","name":"Johannes Berg"},"message":"CHROMIUM: iwl7000: fix LED Kconfig\n\nThe \"select LEDS_CLAS\" should of course be \"select LEDS_CLASS\"\nand the symbol shouldn't have the same name as the iwlwifi one.\n\nBUG=chromium:519130\nTEST=make oldconfig and make sure it doesn't report any warnings\nabout this symbol\n\nChange-Id: I623e4ab907e85ca639f86229f73dd6350c1ca113\nReported-by: Daniel Kurtz <djkurtz@chromium.org>\nSigned-off-by: Johannes Berg <johannes.berg@intel.com>\nReviewed-on: https://chromium-review.googlesource.com/292372\nReviewed-by: Sameer Nanda <snanda@chromium.org>","distinct":true,"url":"https://api.github.com/repos/singulared/chromebook-kernel/commits/b9b0e5dd2b3a50025eb48d225c6e281f7b4fbf24"},{"sha":"db4c634e917ac8ee03a43ac654319f2281d1e668","author":{"email":"50cb10d2be062154b17ab4d66a4eab34f1cf1c84@chromium.org","name":"Kees Cook"},"message":"UPSTREAM: crypto: sanitize argument for format string\n\nThe template lookup interface does not provide a way to use format\nstrings, so make sure that the interface cannot be abused accidentally.\n\nSigned-off-by: Kees Cook <keescook@chromium.org>\nCc: Herbert Xu <herbert@gondor.apana.org.au>\nCc: \"David S. Miller\" <davem@davemloft.net>\nCc: <stable@vger.kernel.org>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\n(cherry picked from commit 1c8fca1d92e14859159a82b8a380d220139b7344)\n\nBUG=chromium:462835\nTEST=kernel_CryptoAPI\n\nChange-Id: I13fc93b40403e97fe7b300f880a57dad05f3eaad\nSigned-off-by: Brian Norris <briannorris@chromium.org>\nReviewed-on: https://chromium-review.googlesource.com/290233\nReviewed-by: Kees Cook <keescook@chromium.org>","distinct":true,"url":"https://api.github.com/repos/singulared/chromebook-kernel/commits/db4c634e917ac8ee03a43ac654319f2281d1e668"},{"sha":"24a986ba19c805ef1917a65550a2a09552cded54","author":{"email":"50cb10d2be062154b17ab4d66a4eab34f1cf1c84@chromium.org","name":"Kees Cook"},"message":"BACKPORT: crypto: prefix module autoloading with \"crypto-\"\n\nThis prefixes all crypto module loading with \"crypto-\" so we never run\nthe risk of exposing module auto-loading to userspace via a crypto API,\nas demonstrated by Mathias Krause:\n\nhttps://lkml.org/lkml/2013/3/4/70\n\nSigned-off-by: Kees Cook <keescook@chromium.org>\nSigned-off-by: Herbert Xu <herbert@gondor.apana.org.au>\n(cherry picked from commit 5d26a105b5a73e5635eae0629b42fa0a90e07b7b)\n\nConflicts:\n\tarch/arm/crypto/sha1_neon_glue.c\n\tarch/arm/crypto/sha512_neon_glue.c\n\tarch/arm64/crypto/aes-ce-ccm-glue.c\n\tarch/arm64/crypto/aes-glue.c\n\tarch/powerpc/crypto/sha1.c\n\tarch/x86/crypto/camellia_aesni_avx2_glue.c\n\tarch/x86/crypto/crc32-pclmul_glue.c\n\tarch/x86/crypto/crct10dif-pclmul_glue.c\n\tarch/x86/crypto/des3_ede_glue.c\n\tarch/x86/crypto/serpent_avx2_glue.c\n\tarch/x86/crypto/sha256_ssse3_glue.c\n\tarch/x86/crypto/sha512_ssse3_glue.c\n\tcrypto/crc32.c\n\tcrypto/crc32c_generic.c\n\tcrypto/crct10dif_generic.c\n\tcrypto/lz4.c\n\tcrypto/lz4hc.c\n\tdrivers/crypto/qat/qat_common/adf_ctl_drv.c\n\tdrivers/s390/crypto/ap_bus.c\n\nBUG=chromium:462835\nTEST=kernel_CryptoAPI\n\nChange-Id: Iaa441ab00413bfba7dd77f31894b1374eff6892c\nSigned-off-by: Brian Norris <briannorris@chromium.org>\nReviewed-on: https://chromium-review.googlesource.com/290234\nReviewed-by: Kees Cook <keescook@chromium.org>","distinct":true,"url":"https://api.github.com/repos/singulared/chromebook-kernel/commits/24a986ba19c805ef1917a65550a2a09552cded54"},{"sha":"9d9cb108bda011ae2d20bb7d2033e143b2774840","author":{"email":"50cb10d2be062154b17ab4d66a4eab34f1cf1c84@chromium.org","name":"Kees Cook"},"message":"BACKPORT: crypto: include crypto- module prefix in template\n\nThis adds the module loading prefix \"crypto-\" to the template lookup\nas well.\n\nFor example, attempting to load 'vfat(blowfish)' via AF_ALG now correctly\nincludes the \"crypto-\" prefix at every level, correctly rejecting \"vfat\":\n\n\tnet-pf-38\n\talgif-hash\n\tcrypto-vfat(blowfish)\n\tcrypto-vfat(blowfish)-all\n\tcrypto-vfat\n\nReported-by: Mathias Krause <minipli@googlemail.com>\nSigned-off-by: Kees Cook <keescook@chromium.org>\nAcked-by: Mathias Krause <minipli@googlemail.com>\nSigned-off-by: Herbert Xu <herbert@gondor.apana.org.au>\n(cherry picked from commit 4943ba16bbc2db05115707b3ff7b4874e9e3c560)\n\nConflicts:\n\tcrypto/mcryptd.c\n\nBUG=chromium:462835\nTEST=kernel_CryptoAPI\n\nChange-Id: Ie8888816cb3872e15d2166888e9c3c9974b3f826\nSigned-off-by: Brian Norris <briannorris@chromium.org>\nReviewed-on: https://chromium-review.googlesource.com/290235\nReviewed-by: Kees Cook <keescook@chromium.org>","distinct":true,"url":"https://api.github.com/repos/singulared/chromebook-kernel/commits/9d9cb108bda011ae2d20bb7d2033e143b2774840"},{"sha":"9a0daad972800226ebd2d950dc6d6d7cf4aeae22","author":{"email":"64568d9183dcfcdd0a6fb47964820a1cdaf94ecc@googlemail.com","name":"Mathias Krause"},"message":"BACKPORT: crypto: add missing crypto module aliases\n\nCommit 5d26a105b5a7 (\"crypto: prefix module autoloading with \"crypto-\"\")\nchanged the automatic module loading when requesting crypto algorithms\nto prefix all module requests with \"crypto-\". This requires all crypto\nmodules to have a crypto specific module alias even if their file name\nwould otherwise match the requested crypto algorithm.\n\nEven though commit 5d26a105b5a7 added those aliases for a vast amount of\nmodules, it was missing a few. Add the required MODULE_ALIAS_CRYPTO\nannotations to those files to make them get loaded automatically, again.\nThis fixes, e.g., requesting 'ecb(blowfish-generic)', which used to work\nwith kernels v3.18 and below.\n\nAlso change MODULE_ALIAS() lines to MODULE_ALIAS_CRYPTO(). The former\nwon't work for crypto modules any more.\n\nFixes: 5d26a105b5a7 (\"crypto: prefix module autoloading with \"crypto-\"\")\nCc: Kees Cook <keescook@chromium.org>\nSigned-off-by: Mathias Krause <minipli@googlemail.com>\nSigned-off-by: Herbert Xu <herbert@gondor.apana.org.au>\n(cherry picked from commit 3e14dcf7cb80b34a1f38b55bc96f02d23fdaaaaf)\n\nConflicts:\n\tarch/powerpc/crypto/sha1.c\n\tarch/x86/crypto/sha-mb/sha1_mb.c\n\tcrypto/crc32c_generic.c [--> crypto/crc32c.c]\n\tcrypto/crct10dif_generic.c\n\nBUG=chromium:462835\nTEST=kernel_CryptoAPI\n\nChange-Id: Id7f097499122263aa422429eeee5b27c033f4084\nSigned-off-by: Brian Norris <briannorris@chromium.org>\nReviewed-on: https://chromium-review.googlesource.com/290236\nReviewed-by: Kees Cook <keescook@chromium.org>","distinct":true,"url":"https://api.github.com/repos/singulared/chromebook-kernel/commits/9a0daad972800226ebd2d950dc6d6d7cf4aeae22"},{"sha":"48024241f352626410ee151b343c447d3358a795","author":{"email":"67059238af8e1945c40edb274ce1d51ba595dbf3@chromium.org","name":"Brian Norris"},"message":"CHROMIUM: config: add crypto UAPI to base config\n\nNeeded for recent bluez\n\nBUG=chromium:462835\nTEST=kernel_CryptoAPI; booted with snow\n\nChange-Id: I0221daf735710c0de8bfd222244f17425c6a1660\nSigned-off-by: Brian Norris <briannorris@chromium.org>\nReviewed-on: https://chromium-review.googlesource.com/290237\nReviewed-by: Kees Cook <keescook@chromium.org>","distinct":true,"url":"https://api.github.com/repos/singulared/chromebook-kernel/commits/48024241f352626410ee151b343c447d3358a795"},{"sha":"5ed07d4604cc2d8cb1610007abadf8d29c496fa3","author":{"email":"9bf1de3f247c5d3b495d8f9e25a7c0f96dce3ad4@xes-inc.com","name":"Peter Tyser"},"message":"UPSTREAM: mfd: lpc_ich: Add support for NM10 GPIO\n\nThe NM10's GPIO is compatible with ICH v7 GPIO.\n\nBUG=chromium:491407\nTEST=boot zgb-x86_freon with HDMI monitor attached\n\nSigned-off-by: Peter Tyser <ptyser@xes-inc.com>\nTested-by: Dan Weinlader <danw@vs-networks.com>\nReviewed-by: Guenter Roeck <linux@roeck-us.net>\nSigned-off-by: Lee Jones <lee.jones@linaro.org>\n(cherry picked from commit 117bbfe25cfc2e968be1f7976ac460a5cd3d734e)\nSigned-off-by: Dominik Behr <dbehr@chromium.org>\n\nChange-Id: I38bc2dd587fedd5395246ff30992f7e1eff3577c\nReviewed-on: https://chromium-review.googlesource.com/293581\nCommit-Queue: Dominik Behr <dbehr@chromium.org>\nTrybot-Ready: Dominik Behr <dbehr@chromium.org>\nTested-by: Dominik Behr <dbehr@chromium.org>\nReviewed-by: Stéphane Marchesin <marcheu@chromium.org>","distinct":true,"url":"https://api.github.com/repos/singulared/chromebook-kernel/commits/5ed07d4604cc2d8cb1610007abadf8d29c496fa3"},{"sha":"810c3911150e4e69e74011dc126e31dd40212ad4","author":{"email":"e7ce582c7d62326af1f467203edc40f69ba4f78f@chromium.org","name":"Dominik Behr"},"message":"CHROMIUM: mfd: lpc_ich: add exception for GPIO conflict for ZGB\n\nBUG=chromium:491407\nTEST=bood zgb-x86_freon with HDMI monitor attached\n\nChange-Id: I20e3f4564e9e1593babfc3fc617cd8775077025c\nSigned-off-by: Dominik Behr <dbehr@chromium.org>\nReviewed-on: https://chromium-review.googlesource.com/293582\nReviewed-by: Stéphane Marchesin <marcheu@chromium.org>","distinct":true,"url":"https://api.github.com/repos/singulared/chromebook-kernel/commits/810c3911150e4e69e74011dc126e31dd40212ad4"},{"sha":"9ad32fc92950b1aa454cb5799d8738f766c75aea","author":{"email":"8f90f27034be8848ddb4e9bbc176b939aee25e93@chromium.org","name":"Wu-Cheng Li"},"message":"CHROMIUM: [media] s5p-mfc: reduce interrupt and watchdog timeout to 1s.\n\nMFC watchdog timeout was 10 seconds and interrupt timeout was 2\nseconds. One MFC command shouldn't take such a long time. Change\nboth timeouts to 1 second.\n\nBUG=chromium:481462\nTEST=Run apprtc loopback and play a video. Run VDA and VEA tests.\n\nChange-Id: I20995b015216906032cddb8c96d7aec0d7e33bbe\nSigned-off-by: Wu-Cheng Li <wuchengli@chromium.org>\nReviewed-on: https://chromium-review.googlesource.com/292055","distinct":true,"url":"https://api.github.com/repos/singulared/chromebook-kernel/commits/9ad32fc92950b1aa454cb5799d8738f766c75aea"},{"sha":"6464863c707be6db82dea6a29154a234f805144c","author":{"email":"e7ce582c7d62326af1f467203edc40f69ba4f78f@chromium.org","name":"Dominik Behr"},"message":"CHROMIUM: config: disable NM10_GPIO and enable GPIO_ICH\n\nNM10_GPIO is outdated and it conflicts with LPC_ICH driver. GPIO_ICH\nexposes the same GPIOs while cooperating with LPC_ICH driver.\n\nBUG=chromium:491407\nTEST=boot xgb-x86_freon with HDMI monitor attached\nCQ-DEPEND=CL:293574\n\nChange-Id: I898ae4cfad45b5cc487541b527f46e4732e4af57\nSigned-off-by: Dominik Behr <dbehr@chromium.org>\nReviewed-on: https://chromium-review.googlesource.com/293583\nReviewed-by: Stéphane Marchesin <marcheu@chromium.org>","distinct":true,"url":"https://api.github.com/repos/singulared/chromebook-kernel/commits/6464863c707be6db82dea6a29154a234f805144c"}]}