{"push_id":1058302000,"size":31,"distinct_size":0,"ref":"refs/heads/chromium-googlesource-kernel-next/chromeos-base-4.4","head":"d523a3240e2d108926595e6572e8303760b37c5b","before":"93b08609204b5aaa81727b0a69024a237e9e6348","commits":[{"sha":"8c8be25b6398aa2acf3e81f36366df4e4472a130","author":{"email":"d867fc987a366be56684d1145622524a3ba1efbf@chromium.org","name":"Sonny Rao"},"message":"CHROMIUM: config: add configuration files and infrastructure\n\nChange-Id: I278e56e1014c19eac845fa39ca61f1f68c43c7e3\n[sonnyrao: 3.8: drop stuff from drivers/Kconfig and drivers/gpu/drm/Kconfig]\nSigned-off-by: Olof Johansson <olofj@chromium.org>\n\n[benzh: 3.14 rebase. Squashed\nCHROMIUM: config: enable ramoops\nCHROMIUM: enable ATH9K_PCI for i386 and x86_64\n]\nSigned-off-by: Ben Zhang <benzh@chromium.org>\n\n[rebase44(filbranden): Squashed it all, removed no longer relevant chips.\n Also fixed the name of some CONFIG_MFD_CROS_EC_* -> CONFIG_CROS_EC_*\n options that got renamed upstream.]\nSigned-off-by: Filipe Brandenburger <filbranden@chromium.org>","distinct":false,"url":"https://api.github.com/repos/olivieer/kernel_msm/commits/8c8be25b6398aa2acf3e81f36366df4e4472a130"},{"sha":"55f9af274a98b291a19ca0c837f10c105ccd1db7","author":{"email":"8f3f75c74bd5184edcfa6534cab3c13a00a2f794@chromium.org","name":"Mike Frysinger"},"message":"CHROMIUM: add PRESUBMIT.cfg to disable various checks\n\nThis makes it so that we don't need to run 'repo upload --no-verify'.\n\nBUG=chromium:411452\nTEST=ran upload on some CLs\n\nChange-Id: I094dd90548a4722115a6d4d21ba8b4ef86b00c54\nSigned-off-by: Mike Frysinger <vapier@chromium.org>\nReviewed-on: https://chromium-review.googlesource.com/217026\nReviewed-by: Chirantan Ekbote <chirantan@chromium.org>","distinct":false,"url":"https://api.github.com/repos/olivieer/kernel_msm/commits/55f9af274a98b291a19ca0c837f10c105ccd1db7"},{"sha":"5820004e4060012f9c8ce713be727df6dfb43d05","author":{"email":"5515d6d2d0829cbe0dd0dcf2094aaded06d58514@chromium.org","name":"vbendeb"},"message":"CHROMIUM: Ignore the top level build/ directory tree.\n\nThis tree is generated by gentoo tools and should be ignored by git.\n\nTested by observing that git does ignore the top level build/ tree,\nbut does report build/ subtrees within the kernel tree.\n\nReview URL: http://codereview.chromium.org/2512002\n\nChange-Id: Ic631c4f151f3ecaa1112b0129bf5841e9e1b3ba0","distinct":false,"url":"https://api.github.com/repos/olivieer/kernel_msm/commits/5820004e4060012f9c8ce713be727df6dfb43d05"},{"sha":"944ba813384449b4b98cf331cf13d4b9d2c2ad5b","author":{"email":"d867fc987a366be56684d1145622524a3ba1efbf@chromium.org","name":"Sonny Rao"},"message":"CHROMIUM: add test_module module\n\nCreate a module for simple module loading tests.\n\nBUG=chromium-os:37353\nTEST=daisy build, security_ModuleLocking passes when using \"test_module\"\n\nChange-Id: I7ac604b614d69c2f18266a2241a660629b418701\nSigned-off-by: Kees Cook <keescook@chromium.org>\nReviewed-on: https://gerrit.chromium.org/gerrit/39918\nReviewed-by: Grant Grundler <grundler@chromium.org>\nTested-by: Grant Grundler <grundler@chromium.org>\n\nConflicts:\n\tlib/Kconfig.debug\n[rebase44(filbranden): Solved trivial conflicts in ordering entries.]\nSigned-off-by: Filipe Brandenburger <filbranden@chromium.org>","distinct":false,"url":"https://api.github.com/repos/olivieer/kernel_msm/commits/944ba813384449b4b98cf331cf13d4b9d2c2ad5b"},{"sha":"cdaaddd1f92feadbdd0ed45165b56b00b527db5f","author":{"email":"6e405e01d1876cac4b6b5ee28b45a47a1ca2bab5@chromium.org","name":"Simon Que"},"message":"CHROMIUM: Add file containing known smatch errors\n\nThis file contains the known smatch errors in the kernel.  Currently it\ncontains only the errors from i386 boards (i.e. 32-bit x86).  In the\nfuture we should add errors from x86_64 and arm boards.\n\nBUG=chromium-os:37418\nTEST=\"FEATURES=test emerge-mario chromeos-kernel\" runs successfully\nCQ-DEPEND=I9d1f11d00c7852c68d26d0b696bb28e47573e154\n\nChange-Id: If47037fc31960933d18eec5825c996a2035f8f48\nSigned-off-by: Simon Que <sque@chromium.org>\nReviewed-on: https://gerrit.chromium.org/gerrit/40056\nReviewed-by: Mandeep Singh Baines <msb@chromium.org>\n\n[benzh: 3.14 rebase. Squashed smatch error updates]\nSigned-off-by: Ben Zhang <benzh@chromium.org>","distinct":false,"url":"https://api.github.com/repos/olivieer/kernel_msm/commits/cdaaddd1f92feadbdd0ed45165b56b00b527db5f"},{"sha":"ac6b8a7af259d9bfe640cc1616aa7a01efe964ba","author":{"email":"6e405e01d1876cac4b6b5ee28b45a47a1ca2bab5@chromium.org","name":"Simon Que"},"message":"CHROMIUM: chromeos: Add script to update smatch error whitelist\n\nThis script can be used to add known smatch errors for new boards to the\nsmatch error whitelist.  It runs the kernel build and check for each new\nboard and aggregates the new errors into a log file.\n\nBUG=chromium-os:37418\nTEST=Run \"./update_smatch_whitelist x86-generic amd64-generic daisy\"\nMake sure there was a log file produced containing new errors.\n\nChange-Id: I6912b6a0d9b9d577af296b15ef1e356e55a9f3ce\nSigned-off-by: Simon Que <sque@chromium.org>\nReviewed-on: https://gerrit.chromium.org/gerrit/41079\nReviewed-by: Mike Frysinger <vapier@chromium.org>\nReviewed-by: Mandeep Singh Baines <msb@chromium.org>\n\n[benzh: 3.14 rebase. Squashed script fixes]\nSigned-off-by: Ben Zhang <benzh@chromium.org>","distinct":false,"url":"https://api.github.com/repos/olivieer/kernel_msm/commits/ac6b8a7af259d9bfe640cc1616aa7a01efe964ba"},{"sha":"512677a1b78e87a5403385fad9a5a71569bd9528","author":{"email":"13dc431ca3b0f062f888def8f8ec4662ec608f7d@chromium.org","name":"Olof Johansson"},"message":"CHROMIUM: timer: add debug_msleep warnings for long sleeps\n\nI've carried a local patch to WARN_ON() long sleeps in the past, but\nI think it makes sense to just check in a slightly cleaned up version\n(i.e. this) that allows boot-time selection of the level to warn for.\n\nBUG=none\nTEST=edit config.txt, add timer.debug_msleep=100, boot, watch it pop a\n few times in dmesg.\n\nChange-Id: Ibb79dfc1dd7a08b12a14af314c593a985603f5a6\nSigned-off-by: Olof Johansson <olofj@chromium.org>\nReviewed-on: https://gerrit.chromium.org/gerrit/29424\nReviewed-by: Sameer Nanda <snanda@chromium.org>\n\nConflicts:\n\tkernel/timer.c\n[filbranden: 3.18 rebase. Moved from kernel/timer.c to kernel/time/timer.c]\nSigned-off-by: Filipe Brandenburger <filbranden@chromium.org>","distinct":false,"url":"https://api.github.com/repos/olivieer/kernel_msm/commits/512677a1b78e87a5403385fad9a5a71569bd9528"},{"sha":"a73dba3fa2cb8d98d1e5e54eba295466ff1516d4","author":{"email":"10a8c465cefc9bdd6c925e26964d23c90f1141cc@chromium.org","name":"Dmitry Torokhov"},"message":"CHROMIUM: driver-core: add test module for asynchronous probing\n\nThis test module tries to test asynchronous driver probing by having a\ndriver that sleeps for extended period of time (5 secs) in its probe()\nmethod, and measuring time needed to register this driver (with device\nalready registered) and a new device (with driver already registered).\nThe module will fail to load if time spent in register call is more than\nhalf the probing timeout.\n\nAs a sanity check the driver than will try to synchronously register\ndriver and device and fail if registration will take less than half\ntimeout time.\n\nBUG=chromium:415343\nTEST=Compiled and tried loading the driver\n\nChange-Id: I02fcb03221bcb4c46e1116f9c49fb37c8d32a917\nSigned-off-by: Dmitry Torokhov <dtor@chromium.org>\nReviewed-on: https://chromium-review.googlesource.com/219107\nReviewed-by: Olof Johansson <olofj@chromium.org>\n[rebase44(groeck): Address kernel API changes]\nSigned-off-by: Guenter Roeck <groeck@chromium.org>","distinct":false,"url":"https://api.github.com/repos/olivieer/kernel_msm/commits/a73dba3fa2cb8d98d1e5e54eba295466ff1516d4"},{"sha":"dc70df61284c32a244321cf8c663e956429294f7","author":{"email":"625600233cb3bcab32268c17610882e0fdaed295@ubuntu.com","name":"Scott James Remnant"},"message":"UBUNTU: SAUCE: trace: add trace events for open(), exec() and uselib()\n\nBugLink: http://bugs.launchpad.net/bugs/462111\n\nThis patch uses TRACE_EVENT to add tracepoints for the open(),\nexec() and uselib() syscalls so that ureadahead can cheaply trace\nthe boot sequence to determine what to read to speed up the next.\n\nIt's not upstream because it will need to be rebased onto the syscall\ntrace events whenever that gets merged, and is a stop-gap.\n\n[benzh: 3.14 rebase. Squashed 2 warning fixes. Fixed a new incompatible\npointer type error for trace_open_exec() due to upstream change]\n\nChange-Id: I3bb5c3f6c2b4b7cfbe7045e342092a4d652bcef2\nSigned-off-by: Scott James Remnant <scott@ubuntu.com>\nAcked-by: Stefan Bader <stefan.bader@canonical.com>\nAcked-by: Andy Whitcroft <andy.whitcroft@canonical.com>\nSigned-off-by: Stefan Bader <stefan.bader@canonical.com>\nSigned-off-by: Ben Zhang <benzh@chromium.org>\n\nConflicts:\n\tfs/exec.c\n[rebase44(filbranden): Moved the trace_open_exec call to the block where\n fsnotify_open was.]\nSigned-off-by: Filipe Brandenburger <filbranden@chromium.org>","distinct":false,"url":"https://api.github.com/repos/olivieer/kernel_msm/commits/dc70df61284c32a244321cf8c663e956429294f7"},{"sha":"f23e0ee4377742c842ad1b469b21d3bd712cba81","author":{"email":"13dc431ca3b0f062f888def8f8ec4662ec608f7d@chromium.org","name":"Olof Johansson"},"message":"CHROMIUM: trace: add back legacy tracing_enabled attribute\n\nTurns out that ureadahead expects the old attribute to enable\ntracing. While we should fix ureadahead, it's convenient to temporarily\nadd back the old one here in the kernel while that happens.\n\nBUG=chromium:248268\nTEST=boot, make sure ureadahead pack files are generated. Bug to add\nureadahead testcases filed at http://crbug.com/251867\n\nChange-Id: I30af7e53dff48733dcbb26e94e2a96bae186d388\nSigned-off-by: Olof Johansson <olofj@chromium.org>\nReviewed-on: https://gerrit.chromium.org/gerrit/59286\nReviewed-by: Sonny Rao <sonnyrao@chromium.org>\n\nConflicts:\n\tkernel/trace/trace.c\n[rebase44(filbranden): Moved the block to the appropriate location.]\nSigned-off-by: Filipe Brandenburger <filbranden@chromium.org>","distinct":false,"url":"https://api.github.com/repos/olivieer/kernel_msm/commits/f23e0ee4377742c842ad1b469b21d3bd712cba81"},{"sha":"23817ffa8350985c59365e60c4939f4c7d7dd4ff","author":{"email":"85550dee2503cc6ca35639514fa03c6933752df4@chromium.org","name":"Siva Chandra"},"message":"CHROMIUM: Do not force GUID partition with 'gpt' command line option.\n\nBUG=chromium:260040\nTEST=Tested on my pixel device with the problem SD card.\n\nSigned-off-by: Siva Chandra <sivachandra@chromium.org>\nChange-Id: I62560eb69a7cc8816de54a1d5086625f65c0aca9\nReviewed-on: https://gerrit.chromium.org/gerrit/65861\nReviewed-by: Olof Johansson <olofj@chromium.org>","distinct":false,"url":"https://api.github.com/repos/olivieer/kernel_msm/commits/23817ffa8350985c59365e60c4939f4c7d7dd4ff"},{"sha":"8cdbc418f4d569d86f2890686d1eaadc713e64b4","author":{"email":"380081620a7947c89c11153c5513f34019caa923@android.com","name":"Colin Cross"},"message":"CHROMIUM: hardlockup: detect hard lockups without NMIs using secondary cpus\n\nEmulate NMIs on systems where they are not available by using timer\ninterrupts on other cpus.  Each cpu will use its softlockup hrtimer\nto update a per-cpu timestamp and then check the timestamp on the\nnext cpu.\n\nThe emulation uses the softlockup threshold instead of the hardlockup\nthreshold because the implementation runs at the same resolution as\nthe softlockup detector.\n\nThis patch is useful on systems where the hardlockup detector is not\navailable due to a lack of NMIs, for example most ARM SoCs.\nWithout this patch any cpu stuck with interrupts disabled can\ncause a hardware watchdog reset with no debugging information,\nbut with this patch the kernel can detect the lockup and panic,\nwhich can result in useful debugging info.\n\nSigned-off-by: Colin Cross <ccross@android.com>\n(cherry picked from android-exynos-manta-3.4-jb-mr2 commit\n\ta4b412105410659bc134ff003ba98a99a9fff698)\n\nBUG=chrome-os-partner:22017\nTEST=Boot on Snow/Peach. Run any test case and if there is a\nhard lockup, system should throw a panic and dump the PC of all\nCPUs.\n\n[prathyush: rebased to chromeos-3.8 kernel with minor changes]\nChange-Id: I0e8eef72691857e0c3c078548f9dd946042a7249\nSigned-off-by: Prathyush K <prathyush.k@samsung.com>\nReviewed-on: https://chromium-review.googlesource.com/66195\nTested-by: <prathyush@chromium.org>\nReviewed-by: Andrew Bresticker <abrestic@chromium.org>\nCommit-Queue: Andrew Bresticker <abrestic@chromium.org>\nReviewed-by: Doug Anderson <dianders@chromium.org>\nTested-by: Doug Anderson <dianders@chromium.org>","distinct":false,"url":"https://api.github.com/repos/olivieer/kernel_msm/commits/8cdbc418f4d569d86f2890686d1eaadc713e64b4"},{"sha":"023068f26f73b4cc03301623fe3b7c5ac63b8a12","author":{"email":"af0622ab041e8b0f8e5819838dcc93898196e71f@chromium.org","name":"Aaron Durbin"},"message":"CHROMIUM: hung_task: dump all UNINTERUPTIBLE tasks\n\nWhen the panic path is taken for khungtaskd dump all\ntasks with the UNINTERUPTIBLE state. That way, any\ninter-dependent tasks that caused one another to hang\nwill be saved in the crash output.\n\nBUG=chrome-os-partner:24397\nBRANCH=None\nTEST=Manual\n\necho HUNG_TASK > /sys/kernel/debug/provoke_crash/DIRECT' &\necho HUNG_TASK > /sys/kernel/debug/provoke_crash/DIRECT' &\necho HUNG_TASK > /sys/kernel/debug/provoke_crash/DIRECT' &\n\nChecked outout of crash showing stack deduping.\n\nChange-Id: I3d7e62ca3d97b78c897e27b903cebe7da7d66025\nSigned-off-by: Aaron Durbin <adurbin@chromium.org>\nReviewed-on: https://chromium-review.googlesource.com/183593\nReviewed-by: Benson Leung <bleung@chromium.org>","distinct":false,"url":"https://api.github.com/repos/olivieer/kernel_msm/commits/023068f26f73b4cc03301623fe3b7c5ac63b8a12"},{"sha":"cab1a80380ae4556ff37db0cde361c73bdfa8e06","author":{"email":"6be5c96c464778f89679b1062a2e0a6af93d2aa5@google.com","name":"Furquan Shaikh"},"message":"CHROMIUM: pstore: Use memcpy_toio instead of memcpy\n\npersistent_ram_update uses vmap / iomap based on whether the buffer is in memory\nregion or reserved region. However, both map it as non-cacheable memory. For\narmv8 specifically, non-cacheable mapping requests use a memory type that has to\nbe accessed aligned to the request size. memcpy() doesn't guarantee that.\n\nBUG=chrome-os-partner:33676\nTEST=Compiles successfully and ramoops buffer working verified on ryu.\n\nChange-Id: I333205017f989a5826a9a09cdba152391f3ddb17\nSigned-off-by: Furquan Shaikh <furquan@google.com>\nReviewed-on: https://chromium-review.googlesource.com/228856\nReviewed-by: Aaron Durbin <adurbin@chromium.org>\nTested-by: Furquan Shaikh <furquan@chromium.org>\nReviewed-by: Olof Johansson <olofj@chromium.org>\nCommit-Queue: Furquan Shaikh <furquan@chromium.org>","distinct":false,"url":"https://api.github.com/repos/olivieer/kernel_msm/commits/cab1a80380ae4556ff37db0cde361c73bdfa8e06"},{"sha":"f1a7b829329c4531b8fa7acb6d42d3516d6e9369","author":{"email":"a1c52a99f156ff41f0ea478f29291144551a02f6@google.com","name":"David Riley"},"message":"CHROMIUM: generate_its_script.sh: script to help create Image.fit files\n\nHelper scripts which generates an its script suitable for input\nto dtc or mkimage to create a fit image with a kernel and dtbs.\n\nBUG=none\nTEST=none\n\nChange-Id: I7bdb2333ee806930613b269ba10820f1f491ae19\nSigned-off-by: David Riley <davidriley@chromium.org>\nReviewed-on: https://chrome-internal-review.googlesource.com/210619\nReviewed-by: David Riley <davidriley@google.com>\nCommit-Queue: David Riley <davidriley@google.com>\nTested-by: David Riley <davidriley@google.com>\nReviewed-on: https://chromium-review.googlesource.com/267228","distinct":false,"url":"https://api.github.com/repos/olivieer/kernel_msm/commits/f1a7b829329c4531b8fa7acb6d42d3516d6e9369"},{"sha":"04c490675214ddc0afce00f641793c4210d6d184","author":{"email":"3daf6939ed4518939423e49b8a1025b098597787@chromium.org","name":"Sameer Nanda"},"message":"CHROMIUM: setlocalversion: check for .scmversion in output dir also\n\nLook for .scmversion file in output directory in addition to the kernel\nsource tree. This is useful for builds where the output directory is not\nthe same as the kernel source directory. In such cases the .scmversion\nfile can be added/deleted in the output directory with no changes needed\nin the kernel sources directories.\n\nBUG=chrome-os-partner:40556\nTEST=do kernel build for both cros_workon on and non-cros_workon\ncases and verify that the kernel version is of the form 3.18.0 and\ndoesn't include the git hash in the kernel version.\n\nChange-Id: I5d5a0259fe43960d428755205d1db7935b2a7d33\nSigned-off-by: Sameer Nanda <snanda@chromium.org>\nReviewed-on: https://chromium-review.googlesource.com/273276\nReviewed-by: Dmitry Torokhov <dtor@chromium.org>\n\n[rebase44(filbranden): Fixed script to cat the .scmversion found.]\nReviewed-on: https://chromium-review.googlesource.com/333874\nSigned-off-by: Filipe Brandenburger <filbranden@chromium.org>","distinct":false,"url":"https://api.github.com/repos/olivieer/kernel_msm/commits/04c490675214ddc0afce00f641793c4210d6d184"},{"sha":"32afa406ba0194f5a8c1ac3d738b81a6da73e421","author":{"email":"6f9d97df82107736b1c4f0e11d74242c25499ec8@chromium.org","name":"Andrew Bresticker"},"message":"CHROMIUM: fs/pstore: Use memcpy_fromio() to save old ramoops buffer\n\nThe ramoops buffer may be mapped as either I/O memory or uncached\nmemory.  On ARM64, this results in a device-type (strongly-ordered)\nmapping.  Since unnaligned accesses to device-type memory will\ngenerate an alignment fault (regardless of whether or not strict\nalignment checking is enabled), it is not safe to use memcpy().\nmemcpy_fromio() is guaranteed to only use aligned accesses, so use\nthat instead.\n\nBUG=chrome-os-partner:44342\nTEST=Manually insert an unaligned copy from the ramoops buffer and\nobserve that it no longer generates an alignment fault.\n\nChange-Id: Ida6cb9d693f1a555f20e16fce06c967852ed6c68\nSigned-off-by: Andrew Bresticker <abrestic@chromium.org>\nReviewed-on: https://chromium-review.googlesource.com/297216\nCommit-Ready: Puneet Kumar <puneetster@chromium.org>\nReviewed-by: Puneet Kumar <puneetster@chromium.org>","distinct":false,"url":"https://api.github.com/repos/olivieer/kernel_msm/commits/32afa406ba0194f5a8c1ac3d738b81a6da73e421"},{"sha":"983e2fdc41255ece8b77f6e2c5e79f9fc718d975","author":{"email":"6e405e01d1876cac4b6b5ee28b45a47a1ca2bab5@chromium.org","name":"Simon Que"},"message":"CHROMIUM: Add -Werror build option\n\nAdd a config option \"ERROR_ON_WARNING\" that adds the \"-Werror\" flag to\ngcc, which turns warnings into errors.\n\nBUG=chromium:534254\nTEST=CONFIG_ERROR_ON_WARNING becomes available in\n     chromeos/scripts/kernelconfig editconfig\n\nChange-Id: I5ef8bb10807b62b6b175de4d5be126c7d0a918ae\nSigned-off-by: Simon Que <sque@chromium.org>\nReviewed-on: https://chromium-review.googlesource.com/300946\nCommit-Ready: Nicolas Boichat <drinkcat@chromium.org>\nTested-by: Nicolas Boichat <drinkcat@chromium.org>\nReviewed-by: Daniel Kurtz <djkurtz@chromium.org>","distinct":false,"url":"https://api.github.com/repos/olivieer/kernel_msm/commits/983e2fdc41255ece8b77f6e2c5e79f9fc718d975"},{"sha":"0c4e333d1895c57ad7f688ef5520e39a3e8938e3","author":{"email":"e7ce582c7d62326af1f467203edc40f69ba4f78f@chromium.org","name":"Dominik Behr"},"message":"CHROMIUM: firmware: do not install radeon firmware\n\nit has been superceeded by linux-firmware package\n\nBUG=chromium:338504\nTEST=build and install amd64generic kernel, it should not install\nanything to /lib/firmware/radeon\n\n(Change-Id: Ia8fed3f39f75fa480d27baa77ab82e99d4ea99be)\nSigned-off-by: Dominik Behr <dbehr@chromium.org>\nReviewed-on: https://chromium-review.googlesource.com/184962\nReviewed-by: Olof Johansson <olofj@chromium.org>\n(cherry picked from commit 2f3538b5c89db87fe979cb06b1480ae311862304)\nSigned-off-by: Gwendal Grignou <gwendal@chromium.org>\n\nChange-Id: I90d9ed8dc71977e9d132e236f2b1fe73e7c24394\nReviewed-on: https://chromium-review.googlesource.com/322338\nCommit-Ready: Gwendal Grignou <gwendal@chromium.org>\nTested-by: Gwendal Grignou <gwendal@chromium.org>\nReviewed-by: Mike Frysinger <vapier@chromium.org>","distinct":false,"url":"https://api.github.com/repos/olivieer/kernel_msm/commits/0c4e333d1895c57ad7f688ef5520e39a3e8938e3"},{"sha":"c8898a39b6d22de777611dc3201453c883c437d6","author":{"email":"f2c659f01951776204a6c5b902787d9019fbeebd@arndb.de","name":"Arnd Bergmann"},"message":"UPSTREAM: mmc: sh_mmcif: rework dma channel handling\n\nWhen compiling the sh_mmcif driver for ARM64, we currently\nget a harmless build warning:\n\n../drivers/mmc/host/sh_mmcif.c: In function 'sh_mmcif_request_dma_one':\n../drivers/mmc/host/sh_mmcif.c:417:4: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]\n    (void *)pdata->slave_id_tx :\n    ^\n../drivers/mmc/host/sh_mmcif.c:418:4: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]\n    (void *)pdata->slave_id_rx;\n\nThis could be worked around by adding another cast to uintptr_t, but\nI decided to simplify the code a little more to avoid that. This\nsplits out the platform data using code into a separate function\nand builds that only for CONFIG_SUPERH. This part still has a typecast\nbut does not need a second one. The SH platform code could be further\nmodified to pass a pointer directly as we do on other architectures\nwhen we have a filter function.\n\nThe normal case is simplified further and now just calls\ndma_request_slave_channel() directly without going through the\ncompat handling.\n\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>\nSigned-off-by: Ulf Hansson <ulf.hansson@linaro.org>\n\n(cherry picked from commit 27cbd7e815a8e223ff7c4fe56daca724101288ac)\nSigned-off-by: Filipe Brandenburger <filbranden@chromium.org>\n\nChange-Id: I105614f941d22c689a067eacf5495cf4222847cc","distinct":false,"url":"https://api.github.com/repos/olivieer/kernel_msm/commits/c8898a39b6d22de777611dc3201453c883c437d6"}]}