{"push_id":2169139193,"size":1000,"distinct_size":0,"ref":"refs/heads/korg/robh/for-next","head":"54192011468dc419aaa8cb3e0c13181112385739","before":"c00758387c3dff94a59fd3521a5ac713c30328af","commits":[{"sha":"d6f295e9def0bee85b37bdffb95153721935c342","author":{"name":"Rasmus Villemoes","email":"177f6c7e7d0681e1b64ab10ef561094344edf6d6@rasmusvillemoes.dk"},"message":"net: core: maybe return -EEXIST in __dev_alloc_name\n\nIf we're given format string with no %d, -EEXIST is a saner error code.\n\nSigned-off-by: Rasmus Villemoes <linux@rasmusvillemoes.dk>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":false,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm-3.18/commits/d6f295e9def0bee85b37bdffb95153721935c342"},{"sha":"87c320e51519a83c496ab7bfb4e96c8f9c001e89","author":{"name":"Rasmus Villemoes","email":"177f6c7e7d0681e1b64ab10ef561094344edf6d6@rasmusvillemoes.dk"},"message":"net: core: dev_get_valid_name is now the same as dev_alloc_name_ns\n\nIf name contains a %, it's easy to see that this patch doesn't change\nanything (other than eliminate the duplicate dev_valid_name\ncall). Otherwise, we'll now just spend a little time in snprintf()\ncopying name to the stack buffer allocated in dev_alloc_name_ns, and do\nthe __dev_get_by_name using that buffer rather than name.\n\nSigned-off-by: Rasmus Villemoes <linux@rasmusvillemoes.dk>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":false,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm-3.18/commits/87c320e51519a83c496ab7bfb4e96c8f9c001e89"},{"sha":"f6b3716dcdcd1a4c3fa05ecb6ab0a1e52b6785d0","author":{"name":"David S. Miller","email":"79caf591e37e1438a2d55ae59670d5cd0d717764@davemloft.net"},"message":"Merge branch 'net-devname_alloc_cleanups'\n\nRasmus Villemoes says:\n\n====================\nnet: core: devname allocation cleanups\n\nIt's somewhat confusing to have both dev_alloc_name and\ndev_get_valid_name. I can't see why the former is less strict than the\nlatter, so make them (or rather dev_alloc_name_ns and\ndev_get_valid_name) equivalent, hardening dev_alloc_name() a little.\n\nObvious follow-up patches would be to only export one function, and\nmake dev_alloc_name a static inline wrapper for that (whichever name\nis chosen for the exported interface). But maybe there is a good\nreason the two exported interfaces do different checking, so I'll\nrefrain from including the trivial but tree-wide renaming in this\nseries.\n====================\n\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":false,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm-3.18/commits/f6b3716dcdcd1a4c3fa05ecb6ab0a1e52b6785d0"},{"sha":"92ee46efeb505ead3ab06d3c5ce695637ed5f152","author":{"name":"Jason Baron","email":"623d78bc3405eaae037ff64ede55814f5ac5c013@akamai.com"},"message":"jump_label: Invoke jump_label_test() via early_initcall()\n\nFengguang Wu reported that running the rcuperf test during boot can cause\nthe jump_label_test() to hit a WARN_ON(). The issue is that the core jump\nlabel code relies on kernel_text_address() to detect when it can no longer\nupdate branches that may be contained in __init sections. The\nkernel_text_address() in turn assumes that if the system_state variable is\ngreter than or equal to SYSTEM_RUNNING then __init sections are no longer\nvalid (since the assumption is that they have been freed). However, when\nrcuperf is setup to run in early boot it can call kernel_power_off() which\nsets the system_state to SYSTEM_POWER_OFF.\n\nSince rcuperf initialization is invoked via a module_init(), we can make\nthe dependency of jump_label_test() needing to complete before rcuperf\nexplicit by calling it via early_initcall().\n\nReported-by: Fengguang Wu <fengguang.wu@intel.com>\nSigned-off-by: Jason Baron <jbaron@akamai.com>\nAcked-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Steven Rostedt <rostedt@goodmis.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nLink: http://lkml.kernel.org/r/1510609727-2238-1-git-send-email-jbaron@akamai.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>","distinct":false,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm-3.18/commits/92ee46efeb505ead3ab06d3c5ce695637ed5f152"},{"sha":"d4bfeabe9ff7967f4b8c24aabf2de1ce3a909cd9","author":{"name":"Thomas Gleixner","email":"352b5f5ba0189d2583768a9bb8247f98115b9038@linutronix.de"},"message":"Merge branch 'linus' into timers/urgent\n\nGet upstream changes so dependent patches can be applied.","distinct":false,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm-3.18/commits/d4bfeabe9ff7967f4b8c24aabf2de1ce3a909cd9"},{"sha":"cb9f780aa93b752ec935e6771a251717d867e603","author":{"name":"Kees Cook","email":"999bfbbf6e15a9d6aba3dfebadcec55340f87c3f@chromium.org"},"message":"s390: qdio: Convert timers to use timer_setup()\n\nIn preparation for unconditionally passing the struct timer_list pointer to\nall timer callbacks, switch to using the new timer_setup() and from_timer()\nto pass the timer pointer explicitly.\n\nCc: Peter Oberparleiter <oberpar@linux.vnet.ibm.com>\nCc: Thomas Gleixner <tglx@linutronix.de>\nSigned-off-by: Kees Cook <keescook@chromium.org>\n[sebott: fixed compile error due to invalid struct member]\nSigned-off-by: Sebastian Ott <sebott@linux.vnet.ibm.com>\nSigned-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>\nSigned-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>","distinct":false,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm-3.18/commits/cb9f780aa93b752ec935e6771a251717d867e603"},{"sha":"846d0c6f794c4bef90a021b18cedde598758507c","author":{"name":"Kees Cook","email":"999bfbbf6e15a9d6aba3dfebadcec55340f87c3f@chromium.org"},"message":"s390/cio: Convert timers to use timer_setup()\n\nIn preparation for unconditionally passing the struct timer_list\npointer to all timer callbacks, switch to using the new timer_setup()\nand from_timer() to pass the timer pointer explicitly.\n\nCc: Sebastian Ott <sebott@linux.vnet.ibm.com>\nCc: Peter Oberparleiter <oberpar@linux.vnet.ibm.com>\nSigned-off-by: Kees Cook <keescook@chromium.org>\nSigned-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>\nSigned-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>","distinct":false,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm-3.18/commits/846d0c6f794c4bef90a021b18cedde598758507c"},{"sha":"c9602ee7d14a72086d10b50ac68e1ea5c01e7579","author":{"name":"Kees Cook","email":"999bfbbf6e15a9d6aba3dfebadcec55340f87c3f@chromium.org"},"message":"s390/sclp: Convert timers to use timer_setup()\n\nIn preparation for unconditionally passing the struct timer_list pointer to\nall timer callbacks, switch to using the new timer_setup() and from_timer()\nto pass the timer pointer explicitly. Instead of creating an external static\ndata variable, just define a separate callback which encodes the \"force\nrestart\" desire.\n\nCc: Peter Oberparleiter <oberpar@linux.vnet.ibm.com>\nCc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Kees Cook <keescook@chromium.org>\n[heiko.carstens@de.ibm.com: get rid of compile warning]\nSigned-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>\nSigned-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>","distinct":false,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm-3.18/commits/c9602ee7d14a72086d10b50ac68e1ea5c01e7579"},{"sha":"cefbeb5df56e1daf0adda8ca5eecee03c5084af6","author":{"name":"Kees Cook","email":"999bfbbf6e15a9d6aba3dfebadcec55340f87c3f@chromium.org"},"message":"s390/ap_bus: Convert timers to use timer_setup()\n\nIn preparation for unconditionally passing the struct timer_list pointer to\nall timer callbacks, switch to using the new timer_setup() and from_timer()\nto pass the timer pointer explicitly.\n\nCc: Harald Freudenberger <freude@de.ibm.com>\nSigned-off-by: Kees Cook <keescook@chromium.org>\nSigned-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>\nSigned-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>","distinct":false,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm-3.18/commits/cefbeb5df56e1daf0adda8ca5eecee03c5084af6"},{"sha":"c771320e9357c9b85634002daedfe5c8988f27a6","author":{"name":"Martin Schwidefsky","email":"9888847d934b0a2b68638ec948181961d68813c8@de.ibm.com"},"message":"s390/mm,kvm: improve detection of KVM guest faults\n\nThe identification of guest fault currently relies on the PF_VCPU flag.\nThis is set in guest_entry_irqoff and cleared in guest_exit_irqoff.\nBoth functions are called by __vcpu_run, the PF_VCPU flag is set for\nquite a lot of kernel code outside of the guest execution.\n\nReplace the PF_VCPU scheme with the PIF_GUEST_FAULT in the pt_regs and\nmake the program check handler code in entry.S set the bit only for\nexception that occurred between the .Lsie_gmap and .Lsie_done labels.\n\nReviewed-by: Christian Borntraeger <borntraeger@de.ibm.com>\nSigned-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>\nSigned-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>","distinct":false,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm-3.18/commits/c771320e9357c9b85634002daedfe5c8988f27a6"},{"sha":"0aaba41b58bc5f3074c0c0a6136b9500b5e29e19","author":{"name":"Martin Schwidefsky","email":"9888847d934b0a2b68638ec948181961d68813c8@de.ibm.com"},"message":"s390: remove all code using the access register mode\n\nThe vdso code for the getcpu() and the clock_gettime() call use the access\nregister mode to access the per-CPU vdso data page with the current code.\n\nAn alternative to the complicated AR mode is to use the secondary space\nmode. This makes the vdso faster and quite a bit simpler. The downside is\nthat the uaccess code has to be changed quite a bit.\n\nWhich instructions are used depends on the machine and what kind of uaccess\noperation is requested. The instruction dictates which ASCE value needs\nto be loaded into %cr1 and %cr7.\n\nThe different cases:\n\n* User copy with MVCOS for z10 and newer machines\n  The MVCOS instruction can copy between the primary space (aka user) and\n  the home space (aka kernel) directly. For set_fs(KERNEL_DS) the kernel\n  ASCE is loaded into %cr1. For set_fs(USER_DS) the user space is already\n  loaded in %cr1.\n\n* User copy with MVCP/MVCS for older machines\n  To be able to execute the MVCP/MVCS instructions the kernel needs to\n  switch to primary mode. The control register %cr1 has to be set to the\n  kernel ASCE and %cr7 to either the kernel ASCE or the user ASCE dependent\n  on set_fs(KERNEL_DS) vs set_fs(USER_DS).\n\n* Data access in the user address space for strnlen / futex\n  To use \"normal\" instruction with data from the user address space the\n  secondary space mode is used. The kernel needs to switch to primary mode,\n  %cr1 has to contain the kernel ASCE and %cr7 either the user ASCE or the\n  kernel ASCE, dependent on set_fs.\n\nTo load a new value into %cr1 or %cr7 is an expensive operation, the kernel\ntries to be lazy about it. E.g. for multiple user copies in a row with\nMVCP/MVCS the replacement of the vdso ASCE in %cr7 with the user ASCE is\ndone only once. On return to user space a CPU bit is checked that loads the\nvdso ASCE again.\n\nTo enable and disable the data access via the secondary space two new\nfunctions are added, enable_sacf_uaccess and disable_sacf_uaccess. The fact\nthat a context is in secondary space uaccess mode is stored in the\nmm_segment_t value for the task. The code of an interrupt may use set_fs\nas long as it returns to the previous state it got with get_fs with another\ncall to set_fs. The code in finish_arch_post_lock_switch simply has to do a\nset_fs with the current mm_segment_t value for the task.\n\nFor CPUs with MVCOS:\n\nCPU running in                        | %cr1 ASCE | %cr7 ASCE |\n--------------------------------------|-----------|-----------|\nuser space                            |  user     |  vdso     |\nkernel, USER_DS, normal-mode          |  user     |  vdso     |\nkernel, USER_DS, normal-mode, lazy    |  user     |  user     |\nkernel, USER_DS, sacf-mode            |  kernel   |  user     |\nkernel, KERNEL_DS, normal-mode        |  kernel   |  vdso     |\nkernel, KERNEL_DS, normal-mode, lazy  |  kernel   |  kernel   |\nkernel, KERNEL_DS, sacf-mode          |  kernel   |  kernel   |\n\nFor CPUs without MVCOS:\n\nCPU running in                        | %cr1 ASCE | %cr7 ASCE |\n--------------------------------------|-----------|-----------|\nuser space                            |  user     |  vdso     |\nkernel, USER_DS, normal-mode          |  user     |  vdso     |\nkernel, USER_DS, normal-mode lazy     |  kernel   |  user     |\nkernel, USER_DS, sacf-mode            |  kernel   |  user     |\nkernel, KERNEL_DS, normal-mode        |  kernel   |  vdso     |\nkernel, KERNEL_DS, normal-mode, lazy  |  kernel   |  kernel   |\nkernel, KERNEL_DS, sacf-mode          |  kernel   |  kernel   |\n\nThe lines with \"lazy\" refer to the state after a copy via the secondary\nspace with a delayed reload of %cr1 and %cr7.\n\nThere are three hardware address spaces that can cause a DAT exception,\nprimary, secondary and home space. The exception can be related to\nfour different fault types: user space fault, vdso fault, kernel fault,\nand the gmap faults.\n\nDependent on the set_fs state and normal vs. sacf mode there are a number\nof fault combinations:\n\n1) user address space fault via the primary ASCE\n2) gmap address space fault via the primary ASCE\n3) kernel address space fault via the primary ASCE for machines with\n   MVCOS and set_fs(KERNEL_DS)\n4) vdso address space faults via the secondary ASCE with an invalid\n   address while running in secondary space in problem state\n5) user address space fault via the secondary ASCE for user-copy\n   based on the secondary space mode, e.g. futex_ops or strnlen_user\n6) kernel address space fault via the secondary ASCE for user-copy\n   with secondary space mode with set_fs(KERNEL_DS)\n7) kernel address space fault via the primary ASCE for user-copy\n   with secondary space mode with set_fs(USER_DS) on machines without\n   MVCOS.\n8) kernel address space fault via the home space ASCE\n\nReplace user_space_fault() with a new function get_fault_type() that\ncan distinguish all four different fault types.\n\nWith these changes the futex atomic ops from the kernel and the\nstrnlen_user will get a little bit slower, as well as the old style\nuaccess with MVCP/MVCS. All user accesses based on MVCOS will be as\nfast as before. On the positive side, the user space vdso code is a\nlot faster and Linux ceases to use the complicated AR mode.\n\nReviewed-by: Heiko Carstens <heiko.carstens@de.ibm.com>\nSigned-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>\nSigned-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>","distinct":false,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm-3.18/commits/0aaba41b58bc5f3074c0c0a6136b9500b5e29e19"},{"sha":"11776eaa6568f5357542bf41b0c7bb90854137cc","author":{"name":"Vasily Gorbik","email":"3b830e88501b966ecd0c0f4be09c49e1a5345e4f@linux.vnet.ibm.com"},"message":"s390: correct some inline assembly constraints\n\nInline assembly code changed in this patch should really use \"Q\"\nconstraint \"Memory reference without index register and with short\ndisplacement\". The kernel does not compile with kasan support enabled\notherwise (due to stack instrumentation).\n\nSigned-off-by: Vasily Gorbik <gor@linux.vnet.ibm.com>\nSigned-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>","distinct":false,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm-3.18/commits/11776eaa6568f5357542bf41b0c7bb90854137cc"},{"sha":"dfd4c4935de8ac39f22e0f65972140405fd27942","author":{"name":"Vasily Gorbik","email":"3b830e88501b966ecd0c0f4be09c49e1a5345e4f@linux.vnet.ibm.com"},"message":"s390/kbuild: get rid of a warning when compiling with KCOV\n\nThis change fixes the following warning:\nwarning: (KCOV) selects GCC_PLUGINS which has unmet direct dependencies\n(HAVE_GCC_PLUGINS && !COMPILE_TEST)\n\nSigned-off-by: Vasily Gorbik <gor@linux.vnet.ibm.com>\nSigned-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>","distinct":false,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm-3.18/commits/dfd4c4935de8ac39f22e0f65972140405fd27942"},{"sha":"838bee9e756ec46e9b5be25f9e44388d7e185a2a","author":{"name":"Jan Kara","email":"7bb7087018cc5fef3c041f6f038f586664845dbf@suse.cz"},"message":"Merge udf, isofs, quota, ext2 changes for 4.15-rc1.","distinct":false,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm-3.18/commits/838bee9e756ec46e9b5be25f9e44388d7e185a2a"},{"sha":"558de28249508dc3ec0ec8981d1315eb8b63f0d9","author":{"name":"Benjamin Gaignard","email":"503651f95c80576ba5d265f11283dd3d5e476501@linaro.org"},"message":"clocksource/timer_of: Rename timer_of_exit to timer_of_cleanup\n\nChange the function name to something more explicit since it is only used\nin init error cases.\n\nAdd __init annotation and description about the function usage.\n\nSigned-off-by: Benjamin Gaignard <benjamin.gaignard@linaro.org>\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nCc: mark.rutland@arm.com\nCc: devicetree@vger.kernel.org\nCc: alexandre.torgue@st.com\nCc: arnd@arndb.de\nCc: julien.thierry@arm.com\nCc: daniel.lezcano@linaro.org\nCc: linux@armlinux.org.uk\nCc: robh+dt@kernel.org\nCc: linux-arm-kernel@lists.infradead.org\nCc: mcoquelin.stm32@gmail.com\nCc: sudeep.holla@arm.com\nCc: ludovic.barre@st.com\nLink: https://lkml.kernel.org/r/1510649563-22975-2-git-send-email-benjamin.gaignard@linaro.org","distinct":false,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm-3.18/commits/558de28249508dc3ec0ec8981d1315eb8b63f0d9"},{"sha":"aea3706cfc4d952ed6d32b6d5845b5ecd99ed7f5","author":{"name":"Miroslav Lichvar","email":"dff4e058f2aa89d1c9e462ceed29e4a5f113691a@redhat.com"},"message":"timekeeping: Remove CONFIG_GENERIC_TIME_VSYSCALL_OLD\n\nAs of d4d1fc61eb38f (ia64: Update fsyscall gettime to use modern\nvsyscall_update)the last user of CONFIG_GENERIC_TIME_VSYSCALL_OLD\nhave been updated, the legacy support for old-style vsyscall\nimplementations can be removed from the timekeeping code.\n\n(Thanks again to Tony Luck for helping remove the last user!)\n\n[jstultz: Commit message rework]\n\nSigned-off-by: Miroslav Lichvar <mlichvar@redhat.com>\nSigned-off-by: John Stultz <john.stultz@linaro.org>\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nCc: Prarit Bhargava <prarit@redhat.com>\nCc: Tony Luck <tony.luck@intel.com>\nCc: Richard Cochran <richardcochran@gmail.com>\nCc: Stephen Boyd <stephen.boyd@linaro.org>\nLink: https://lkml.kernel.org/r/1510613491-16695-1-git-send-email-john.stultz@linaro.org","distinct":false,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm-3.18/commits/aea3706cfc4d952ed6d32b6d5845b5ecd99ed7f5"},{"sha":"41cc30412d6692c25506bf2d4e65c4364c70c10a","author":{"name":"Thomas Gleixner","email":"352b5f5ba0189d2583768a9bb8247f98115b9038@linutronix.de"},"message":"Merge tag 'irqchip-4.15-4' of git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms into irq/urgent\n\nPull irqchip updates for 4.15, take #4 from Marc Zyngier\n\n - A core irq fix for legacy cases where the irq trigger is not reported\n   by firmware\n\n - A couple of GICv3/4 fixes (Kconfig, of-node refcount, error handling)\n\n - Trivial pr_err fixes","distinct":false,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm-3.18/commits/41cc30412d6692c25506bf2d4e65c4364c70c10a"},{"sha":"0e54705b0e01dcaf3eb2a496bb66d5f05012056b","author":{"name":"Wei Yongjun","email":"cea121043064f325ec96cf17db61a214210a3ed7@huawei.com"},"message":"irqchip/exiu: Fix return value check in exiu_init()\n\nIn case of error, the function of_iomap() returns NULL pointer not\nERR_PTR().\n\nReplace the IS_ERR() test of the return value with NULL test and return\na proper error code.\n\nFixes: 706cffc1b912 (\"irqchip/exiu: Add support for Socionext Synquacer EXIU controller\")\nSigned-off-by: Wei Yongjun <weiyongjun1@huawei.com>\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nAcked-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>\nCc: Marc Zyngier <marc.zyngier@arm.com>\nCc: Jason Cooper <jason@lakedaemon.net>\nLink: https://lkml.kernel.org/r/1510642648-123574-1-git-send-email-weiyongjun1@huawei.com","distinct":false,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm-3.18/commits/0e54705b0e01dcaf3eb2a496bb66d5f05012056b"},{"sha":"09e15086936e01d7588020be37ea724116bcefec","author":{"name":"Xiongfeng Wang","email":"ff92437fb5541a8ea467c80058e186b5698fa9f9@huawei.com"},"message":"ACPI / utils: Fix memory leak in acpi_evaluate_reference() error path\n\nWhen package.count is larger than ACPI_MAX_HANDLES, buffer.pointer is\nnot freed before the function returns AE_NO_MEMORY. Fix this possible\nmemory leak by kfree'ing it.\n\nSigned-off-by: Xiongfeng Wang <wangxiongfeng2@huawei.com>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>","distinct":false,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm-3.18/commits/09e15086936e01d7588020be37ea724116bcefec"},{"sha":"3ba88c477bac891a53ba5a0efb351285297a5e5b","author":{"name":"Harald Welte","email":"1bea0d4f31c8562ffb1eea349653b7434bf390c6@gnumonks.org"},"message":"net: Extend Kernel GTP-U tunneling documentation\n\n* clarify specification references for v0/v1\n* add section \"APN vs. Network device\"\n* add section \"Local GTP-U entity and tunnel identification\"\n\nSigned-off-by: Andreas Schultz <aschultz@tpip.net>\nSigned-off-by: Harald Welte <laforge@gnumonks.org>\nSigned-off-by: David S. Miller <davem@davemloft.net>","distinct":false,"url":"https://api.github.com/repos/mifl/android_kernel_qcom_msm-3.18/commits/3ba88c477bac891a53ba5a0efb351285297a5e5b"}]}
{"actor":{"display_login":"mifl"}}