{"push_id":733834336,"size":13,"distinct_size":5,"ref":"refs/heads/linux-master","head":"d725e66c06ab440032f49ef17e960896d0ec6d49","before":"9d634c410b07be7bf637ea03362d3ff132088fe3","commits":[{"sha":"70f19f5869c5accfd9f371c099f21c71516591b2","author":{"email":"9d40d336d058a75e8d7858d87b419b7f640aa15b@digidescorp.com","name":"Steven J. Magnani"},"message":"udf: Don't corrupt unalloc spacetable when writing it\n\nFor a UDF filesystem configured with an Unallocated Space Table,\na filesystem operation that triggers an update to the table results\nin on-disk corruption that prevents remounting:\n\n  udf_read_tagged: tag version 0x0000 != 0x0002 || 0x0003, block 274\n\nFor example:\n  1. Create a filesystem\n      $ mkudffs --media-type=hd --blocksize=512 --lvid=BUGTEST \\\n              --vid=BUGTEST --fsid=BUGTEST --space=unalloctable \\\n              /dev/mmcblk0\n\n  2. Mount it\n      # mount /dev/mmcblk0 /mnt\n\n  3. Create a file\n      $ echo \"No corruption, please\" > /mnt/new.file\n\n  4. Umount\n      # umount /mnt\n\n  5. Attempt remount\n      # mount /dev/mmcblk0 /mnt\n\nThis appears to be a longstanding bug caused by zero-initialization of\nthe Unallocated Space Entry block buffer and only partial repopulation\nof required fields before writing to disk.\n\nCommit 0adfb339fd64 (\"udf: Fix unalloc space handling in udf_update_inode\")\naddressed one such field, but several others are required.\n\nSigned-off-by: Steven J. Magnani <steve@digidescorp.com>\nSigned-off-by: Jan Kara <jack@suse.com>","distinct":false,"url":"https://api.github.com/repos/RobertCNelson/ti-linux-kernel/commits/70f19f5869c5accfd9f371c099f21c71516591b2"},{"sha":"5cde07abcbc57b3430b044cb2cf028d97d7a7254","author":{"email":"1a8531307367602b8284517edb33d53d54e5ce8e@samsung.com","name":"Krzysztof Kozlowski"},"message":"pinctrl: samsung: Remove old unused defines\n\nSince 9a2c1c3b91aa (\"pinctrl: samsung: Allow grouping multiple\npinmux/pinconf nodes\") the defines for GPIO group and function names are\nnot used anywhere in the driver.\n\nSigned-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>\nInspired-by: Dan Carpenter <dan.carpenter@oracle.com>\nSigned-off-by: Linus Walleij <linus.walleij@linaro.org>","distinct":false,"url":"https://api.github.com/repos/RobertCNelson/ti-linux-kernel/commits/5cde07abcbc57b3430b044cb2cf028d97d7a7254"},{"sha":"d6726c8145290bef950ae2538ea6ae1d96a1944b","author":{"email":"43232e92d70cc7aa53504ad0397085ee47bad87f@goodmis.org","name":"Steven Rostedt (Red Hat)"},"message":"tracing: Fix sample output of dynamic arrays\n\nHe Kuang noticed that the trace event samples for arrays was broken:\n\n\"The output result of trace_foo_bar event in traceevent samples is\n wrong. This problem can be reproduced as following:\n\n  (Build kernel with SAMPLE_TRACE_EVENTS=m)\n\n  $ insmod trace-events-sample.ko\n\n  $ echo 1 > /sys/kernel/debug/tracing/events/sample-trace/foo_bar/enable\n\n  $ cat /sys/kernel/debug/tracing/trace\n\n  event-sample-980 [000] ....  43.649559: foo_bar: foo hello 21 0x15\n  BIT1|BIT3|0x10 {0x1,0x6f6f6e53,0xff007970,0xffffffff} Snoopy\n                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n                 The array length is not right, should be {0x1}.\n  (ffffffff,ffffffff)\n\n  event-sample-980 [000] ....  44.653827: foo_bar: foo hello 22 0x16\n  BIT2|BIT3|0x10\n  {0x1,0x2,0x646e6147,0x666c61,0xffffffff,0xffffffff,0x750aeffe,0x7}\n  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n                 The array length is not right, should be {0x1,0x2}.\n  Gandalf (ffffffff,ffffffff)\"\n\nThis was caused by an update to have __print_array()'s second parameter\nbe the count of items in the array and not the size of the array.\n\nAs there is already users of __print_array(), it can not change. But\nthe sample code can and we can also improve on the documentation about\n__print_array() and __get_dynamic_array_len().\n\nLink: http://lkml.kernel.org/r/1436839171-31527-2-git-send-email-hekuang@huawei.com\n\nFixes: ac01ce1410fc2 (\"tracing: Make ftrace_print_array_seq compute buf_len\")\nReported-by: He Kuang <hekuang@huawei.com>\nSigned-off-by: Steven Rostedt <rostedt@goodmis.org>","distinct":true,"url":"https://api.github.com/repos/RobertCNelson/ti-linux-kernel/commits/d6726c8145290bef950ae2538ea6ae1d96a1944b"},{"sha":"27aa2e3a3c99d3319de12ada0d292e33f5831e60","author":{"email":"9cd9d802d23c0ed5e224beabf4ae4a5c478746ef@linaro.org","name":"Linus Walleij"},"message":"pinctrl: abx500: remove strict mode\n\nCommit a21763a0b1e5a5ab8310f581886d04beadc16616\n\"pinctrl: nomadik: activate strict mux mode\"\nput all Nomadik pin controllers to strict mode. This was\nnot good on the Snowball platform: the muxing of GPIOs to\ndifferent pins is done with hogs in the DTS file, and then\nthese GPIOs are used by offset, relying on hogs to mux the\npins. Since that means the pin controller \"owns\" the pins\nand at the same time we have a GPIO user, this pin controller\nis by definition not strict.\n\nSigned-off-by: Linus Walleij <linus.walleij@linaro.org>","distinct":false,"url":"https://api.github.com/repos/RobertCNelson/ti-linux-kernel/commits/27aa2e3a3c99d3319de12ada0d292e33f5831e60"},{"sha":"61bb3aef92a4d102382f399eafccd5c72be6fdf2","author":{"email":"d8c69075be49b0738b690ec4af0e9025b8c97c9e@cogentembedded.com","name":"Sergei Shtylyov"},"message":"sh-pfc: fix sparse GPIOs for R-Car SoCs\n\nThe PFC driver causes the kernel to hang on the R-Car gen2 SoC based  boards\nwhen the CPU_ALL_PORT() macro is fixed to reflect the reality, i.e. when the\nGPIO space becomes actually sparse.  This happens because the _GP_GPIO() macro\nincludes  an indexed initializer which causes the \"holes\" (array entries filled\nwith all 0s) between the groups  of the existing GPIOs; and the driver can't\ncope with that.  There seems to  be no reason to use the indexed initializer,\nso we can remove the index specifier and so avoid the \"holes\".\n\nSigned-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>\nAcked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>\nTested-by: Geert Uytterhoeven <geert+renesas@glider.be>\nSigned-off-by: Linus Walleij <linus.walleij@linaro.org>","distinct":false,"url":"https://api.github.com/repos/RobertCNelson/ti-linux-kernel/commits/61bb3aef92a4d102382f399eafccd5c72be6fdf2"},{"sha":"c10372e615b8f790d30cbfcf59e43908ca42bf1a","author":{"email":"bfa0a1520768723a1c60e18250fb841c342eb8d8@ti.com","name":"Grygorii Strashko"},"message":"pinctrl: single: ensure pcs irq will not be forced threaded\n\nThe PSC IRQ is requested using request_irq() API and as result it can\nbe forced to be threaded IRQ in RT-Kernel if PCS_QUIRK_HAS_SHARED_IRQ\nis enabled for pinctrl domain.\n\nAs result, following 'possible irq lock inversion dependency' report\ncan be seen:\n=========================================================\n[ INFO: possible irq lock inversion dependency detected ]\n3.14.43-rt42-00360-g96ff499-dirty #24 Not tainted\n---------------------------------------------------------\nirq/369-pinctrl/927 just changed the state of lock:\n (&pcs->lock){+.....}, at: [<c0375b54>] pcs_irq_handle+0x48/0x9c\nbut this lock was taken by another, HARDIRQ-safe lock in the past:\n (&irq_desc_lock_class){-.....}\n\nand interrupts could create inverse lock ordering between them.\n\nother info that might help us debug this:\n Possible interrupt unsafe locking scenario:\n\n       CPU0                    CPU1\n       ----                    ----\n  lock(&pcs->lock);\n                               local_irq_disable();\n                               lock(&irq_desc_lock_class);\n                               lock(&pcs->lock);\n  <Interrupt>\n    lock(&irq_desc_lock_class);\n\n *** DEADLOCK ***\n\nno locks held by irq/369-pinctrl/927.\n\nthe shortest dependencies between 2nd lock and 1st lock:\n  -> (&irq_desc_lock_class){-.....} ops: 58724 {\n     IN-HARDIRQ-W at:\n                       [<c0090040>] lock_acquire+0x9c/0x158\n                       [<c07065c8>] _raw_spin_lock+0x48/0x58\n                       [<c009edac>] handle_fasteoi_irq+0x24/0x15c\n                       [<c009abb0>] generic_handle_irq+0x3c/0x4c\n                       [<c000f83c>] handle_IRQ+0x50/0xa0\n                       [<c0008674>] gic_handle_irq+0x3c/0x6c\n                       [<c0707a04>] __irq_svc+0x44/0x8c\n                       [<c000fc44>] arch_cpu_idle+0x40/0x4c\n                       [<c009aadc>] cpu_startup_entry+0x270/0x2e0\n                       [<c06fcbf8>] rest_init+0xd4/0xe4\n                       [<c0a44bfc>] start_kernel+0x3d0/0x3dc\n                       [<80008084>] 0x80008084\n     INITIAL USE at:\n                      [<c0090040>] lock_acquire+0x9c/0x158\n                      [<c070674c>] _raw_spin_lock_irqsave+0x54/0x68\n                      [<c009aff8>] __irq_get_desc_lock+0x64/0xa4\n                      [<c009e38c>] irq_set_chip+0x30/0x78\n                      [<c009ec30>] irq_set_chip_and_handler_name+0x24/0x3c\n                      [<c036ca10>] gic_irq_domain_map+0x48/0xb4\n                      [<c00a0a80>] irq_domain_associate+0x84/0x1d4\n                      [<c00a1154>] irq_create_mapping+0x80/0x11c\n                      [<c00a1270>] irq_create_of_mapping+0x80/0x120\n                      [<c05cdaa8>] irq_of_parse_and_map+0x34/0x3c\n                      [<c0a4ea24>] omap_dm_timer_init_one+0x90/0x30c\n                      [<c0a4eef0>] omap5_realtime_timer_init+0x8c/0x48c\n                      [<c0a486b0>] time_init+0x28/0x38\n                      [<c0a44a6c>] start_kernel+0x240/0x3dc\n                      [<80008084>] 0x80008084\n   }\n   ... key      at: [<c1049ce0>] irq_desc_lock_class+0x0/0x8\n   ... acquired at:\n   [<c07065c8>] _raw_spin_lock+0x48/0x58\n   [<c0375a90>] pcs_irq_unmask+0x58/0xa0\n   [<c009ea48>] irq_enable+0x38/0x48\n   [<c009ead0>] irq_startup+0x78/0x7c\n   [<c009d440>] __setup_irq+0x4a8/0x4f4\n   [<c009d5dc>] request_threaded_irq+0xb8/0x138\n   [<c0415a5c>] omap_8250_startup+0x4c/0x148\n   [<c041276c>] serial8250_startup+0x24/0x30\n   [<c040d0ec>] uart_startup.part.9+0x5c/0x1b4\n   [<c040dbcc>] uart_open+0xf4/0x16c\n   [<c03f0540>] tty_open+0x170/0x61c\n   [<c0157028>] chrdev_open+0xbc/0x1b4\n   [<c0150494>] do_dentry_open+0x1e8/0x2bc\n   [<c0150a84>] finish_open+0x44/0x5c\n   [<c0160d50>] do_last.isra.47+0x710/0xca0\n   [<c01613a4>] path_openat+0xc4/0x640\n   [<c0162904>] do_filp_open+0x3c/0x98\n   [<c0151bdc>] do_sys_open+0x114/0x1d8\n   [<c0151cc8>] SyS_open+0x28/0x2c\n   [<c0a44d70>] kernel_init_freeable+0x168/0x1e4\n   [<c06fcc24>] kernel_init+0x1c/0xf8\n   [<c000eee8>] ret_from_fork+0x14/0x20\n\n-> (&pcs->lock){+.....} ops: 65 {\n   HARDIRQ-ON-W at:\n                    [<c0090040>] lock_acquire+0x9c/0x158\n                    [<c07065c8>] _raw_spin_lock+0x48/0x58\n                    [<c0375b54>] pcs_irq_handle+0x48/0x9c\n                    [<c0375c5c>] pcs_irq_handler+0x1c/0x28\n                    [<c009c458>] irq_forced_thread_fn+0x30/0x74\n                    [<c009c784>] irq_thread+0x158/0x1c4\n                    [<c0063fc4>] kthread+0xd4/0xe8\n                    [<c000eee8>] ret_from_fork+0x14/0x20\n   INITIAL USE at:\n                   [<c0090040>] lock_acquire+0x9c/0x158\n                   [<c070674c>] _raw_spin_lock_irqsave+0x54/0x68\n                   [<c0375344>] pcs_enable+0x7c/0xe8\n                   [<c0372a44>] pinmux_enable_setting+0x178/0x220\n                   [<c036fecc>] pinctrl_select_state+0x110/0x194\n                   [<c04732dc>] pinctrl_bind_pins+0x7c/0x108\n                   [<c045853c>] driver_probe_device+0x70/0x254\n                   [<c0458810>] __driver_attach+0x9c/0xa0\n                   [<c045674c>] bus_for_each_dev+0x78/0xac\n                   [<c0458030>] driver_attach+0x2c/0x30\n                   [<c0457c78>] bus_add_driver+0x15c/0x204\n                   [<c0458ee0>] driver_register+0x88/0x108\n                   [<c045a168>] __platform_driver_register+0x64/0x6c\n                   [<c0a8170c>] omap_hsmmc_driver_init+0x1c/0x20\n                   [<c0008a94>] do_one_initcall+0x110/0x170\n                   [<c0a44d48>] kernel_init_freeable+0x140/0x1e4\n                   [<c06fcc24>] kernel_init+0x1c/0xf8\n                   [<c000eee8>] ret_from_fork+0x14/0x20\n }\n ... key      at: [<c1088a8c>] __key.18572+0x0/0x8\n ... acquired at:\n   [<c008cdd4>] mark_lock+0x388/0x76c\n   [<c008df40>] __lock_acquire+0x6d0/0x1f98\n   [<c0090040>] lock_acquire+0x9c/0x158\n   [<c07065c8>] _raw_spin_lock+0x48/0x58\n   [<c0375b54>] pcs_irq_handle+0x48/0x9c\n   [<c0375c5c>] pcs_irq_handler+0x1c/0x28\n   [<c009c458>] irq_forced_thread_fn+0x30/0x74\n   [<c009c784>] irq_thread+0x158/0x1c4\n   [<c0063fc4>] kthread+0xd4/0xe8\n   [<c000eee8>] ret_from_fork+0x14/0x20\n\nstack backtrace:\nCPU: 1 PID: 927 Comm: irq/369-pinctrl Not tainted 3.14.43-rt42-00360-g96ff499-dirty #24\n[<c00177e0>] (unwind_backtrace) from [<c00130b0>] (show_stack+0x20/0x24)\n[<c00130b0>] (show_stack) from [<c0702958>] (dump_stack+0x84/0xd0)\n[<c0702958>] (dump_stack) from [<c008bcfc>] (print_irq_inversion_bug+0x1d0/0x21c)\n[<c008bcfc>] (print_irq_inversion_bug) from [<c008bf18>] (check_usage_backwards+0xb4/0x11c)\n[<c008bf18>] (check_usage_backwards) from [<c008cdd4>] (mark_lock+0x388/0x76c)\n[<c008cdd4>] (mark_lock) from [<c008df40>] (__lock_acquire+0x6d0/0x1f98)\n[<c008df40>] (__lock_acquire) from [<c0090040>] (lock_acquire+0x9c/0x158)\n[<c0090040>] (lock_acquire) from [<c07065c8>] (_raw_spin_lock+0x48/0x58)\n[<c07065c8>] (_raw_spin_lock) from [<c0375b54>] (pcs_irq_handle+0x48/0x9c)\n[<c0375b54>] (pcs_irq_handle) from [<c0375c5c>] (pcs_irq_handler+0x1c/0x28)\n[<c0375c5c>] (pcs_irq_handler) from [<c009c458>] (irq_forced_thread_fn+0x30/0x74)\n[<c009c458>] (irq_forced_thread_fn) from [<c009c784>] (irq_thread+0x158/0x1c4)\n[<c009c784>] (irq_thread) from [<c0063fc4>] (kthread+0xd4/0xe8)\n[<c0063fc4>] (kthread) from [<c000eee8>] (ret_from_fork+0x14/0x20)\n\nTo fix it use IRQF_NO_THREAD to ensure that pcs irq will not be forced threaded.\n\nCc: Tony Lindgren <tony@atomide.com>\nCc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>\nSigned-off-by: Grygorii Strashko <grygorii.strashko@ti.com>\nAcked-by: Tony Lindgren <tony@atomide.com>\nSigned-off-by: Linus Walleij <linus.walleij@linaro.org>","distinct":false,"url":"https://api.github.com/repos/RobertCNelson/ti-linux-kernel/commits/c10372e615b8f790d30cbfcf59e43908ca42bf1a"},{"sha":"714b1dd8f72e39ef4bc0f38f7f341bb1d57d98bf","author":{"email":"3692bfa45759a67d83aedf0045f6cb635a966abf@raspberrypi.org","name":"Jonathan Bell"},"message":"pinctrl: bcm2835: Clear the event latch register when disabling interrupts\n\nIt's possible to hit a race condition if interrupts are generated on a GPIO\npin when the IRQ line in question is being disabled.\n\nIf the interrupt is freed, bcm2835_gpio_irq_disable() is called which\ndisables the event generation sources (edge, level). If an event occurred\nbetween the last disabling of hard IRQs and the write to the event\nsource registers, a bit would be set in the GPIO event detect register\n(GPEDSn) which goes unacknowledged by bcm2835_gpio_irq_handler()\nso Linux complains loudly.\n\nThere is no per-GPIO mask register, so when disabling GPIO interrupts\nwrite 1 to the relevant bit in GPEDSn to clear out any stale events.\n\nSigned-off-by: Jonathan Bell <jonathan@raspberrypi.org>\nAcked-by: Stephen Warren <swarren@wwwdotorg.org>\nSigned-off-by: Linus Walleij <linus.walleij@linaro.org>","distinct":false,"url":"https://api.github.com/repos/RobertCNelson/ti-linux-kernel/commits/714b1dd8f72e39ef4bc0f38f7f341bb1d57d98bf"},{"sha":"9571b25df1dbf4db17191b54f59734e8b77fd591","author":{"email":"181323dd666a182bc2d953e52d0ac3ab54cd8391@pengutronix.de","name":"Uwe Kleine-König"},"message":"Subject: pinctrl: imx1-core: Fix debug output in .pin_config_set callback\n\nimx1_pinconf_set assumes that the array of pins in struct\nimx1_pinctrl_soc_info can be indexed by pin id to get the\npinctrl_pin_desc for a pin. This used to be correct up to commit\n607af165c047 which removed some entries from the array and so made it\nwrong to access the array by pin id.\n\nThe result of this bug is a wrong pin name in the output for small pin\nids and an oops for the bigger ones.\n\nThis patch is the result of a discussion that includes patches by Markus\nPargmann and Chris Ruehl.\n\nFixes: 607af165c047 (\"pinctrl: i.MX27: Remove nonexistent pad definitions\")\nCc: stable@vger.kernel.org\nReported-by: Chris Ruehl <chris.ruehl@gtsys.com.hk>\nSigned-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>\nReviewed-by: Markus Pargmann <mpa@pengutronix.de>\nSigned-off-by: Linus Walleij <linus.walleij@linaro.org>","distinct":false,"url":"https://api.github.com/repos/RobertCNelson/ti-linux-kernel/commits/9571b25df1dbf4db17191b54f59734e8b77fd591"},{"sha":"681ccdcc756f17f847beba5ac4cd3d03e0949489","author":{"email":"6f54d78a4cd927eb19dd17c34117bfc80f7abcf7@gmail.com","name":"Joachim Eastwood"},"message":"pinctrl: lpc18xx: fix schmitt trigger setup\n\nThe param_val variable is what determines if schmitt\ntrigger is enabled on a pin or not. A typo here mean\nthat schmitt trigger was always enabled for standard\nand i2c pins.\n\nSigned-off-by: Joachim Eastwood <manabian@gmail.com>\nSigned-off-by: Linus Walleij <linus.walleij@linaro.org>","distinct":false,"url":"https://api.github.com/repos/RobertCNelson/ti-linux-kernel/commits/681ccdcc756f17f847beba5ac4cd3d03e0949489"},{"sha":"1ad474de9349870f085b61c90bc80022702a78cc","author":{"email":"69652caca27c8b940640ad396ab71f93cacec34f@linux-foundation.org","name":"Linus Torvalds"},"message":"Merge tag 'trace-v4.2-rc2-fix2' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace\n\nPull tracing sample code fix from Steven Rostedt:\n \"He Kuang noticed that the sample code using the trace_event helper\n  function __get_dynamic_array_len() is broken.\n\n  This only changes the sample code, and I'm pushing this now instead of\n  later because I don't want others using the broken code as an example\n  when using it for real\"\n\n* tag 'trace-v4.2-rc2-fix2' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace:\n  tracing: Fix sample output of dynamic arrays","distinct":true,"url":"https://api.github.com/repos/RobertCNelson/ti-linux-kernel/commits/1ad474de9349870f085b61c90bc80022702a78cc"},{"sha":"8426fb302c964894af15b5052241cf0bf45047bf","author":{"email":"69652caca27c8b940640ad396ab71f93cacec34f@linux-foundation.org","name":"Linus Torvalds"},"message":"Merge branch 'for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs\n\nPull UDF fix from Jan Kara:\n \"A fix for UDF corruption when certain disk-format feature is enabled\"\n\n* 'for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs:\n  udf: Don't corrupt unalloc spacetable when writing it","distinct":true,"url":"https://api.github.com/repos/RobertCNelson/ti-linux-kernel/commits/8426fb302c964894af15b5052241cf0bf45047bf"},{"sha":"71ebd1af094db1c72d69505a27dfecea99c2cb0b","author":{"email":"69652caca27c8b940640ad396ab71f93cacec34f@linux-foundation.org","name":"Linus Torvalds"},"message":"Merge tag 'pinctrl-v4.2-2' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl\n\nPull pin control fixes from Linus Walleij:\n \"Here are some overly ripe pin control fixes for the v4.2 series.\n\n  They got delayed because of various crap commits and having to clean\n  and rinse the patch stack a few times.  Now they are however looking\n  good.\n\n   - some dead defines dropped from the Samsung driver, was targeted for\n     -rc2 but got delayed\n   - drop the strict mode from abx500, this was too strict\n   - fix the R-Car sparse IRQs code to work as intended\n   - fix the IRQ code for the pinctrl-single GPIO backend to not enforce\n     threaded IRQs\n   - clear the latched events/IRQs for the Broadcom BCM2835 driver\n   - fix up debugfs for the Freescale imx1 driver\n   - fix a typo bug in the Schmitt Trigger setup in the LPC18xx driver\"\n\n* tag 'pinctrl-v4.2-2' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl:\n  pinctrl: lpc18xx: fix schmitt trigger setup\n  Subject: pinctrl: imx1-core: Fix debug output in .pin_config_set callback\n  pinctrl: bcm2835: Clear the event latch register when disabling interrupts\n  pinctrl: single: ensure pcs irq will not be forced threaded\n  sh-pfc: fix sparse GPIOs for R-Car SoCs\n  pinctrl: abx500: remove strict mode\n  pinctrl: samsung: Remove old unused defines","distinct":true,"url":"https://api.github.com/repos/RobertCNelson/ti-linux-kernel/commits/71ebd1af094db1c72d69505a27dfecea99c2cb0b"},{"sha":"d725e66c06ab440032f49ef17e960896d0ec6d49","author":{"email":"69652caca27c8b940640ad396ab71f93cacec34f@linux-foundation.org","name":"Linus Torvalds"},"message":"Revert \"fsnotify: fix oops in fsnotify_clear_marks_by_group_flags()\"\n\nThis reverts commit a2673b6e040663bf16a552f8619e6bde9f4b9acf.\n\nKinglong Mee reports a memory leak with that patch, and Jan Kara confirms:\n\n \"Thanks for report! You are right that my patch introduces a race\n  between fsnotify kthread and fsnotify_destroy_group() which can result\n  in leaking inotify event on group destruction.\n\n  I haven't yet decided whether the right fix is not to queue events for\n  dying notification group (as that is pointless anyway) or whether we\n  should just fix the original problem differently...  Whenever I look\n  at fsnotify code mark handling I get lost in the maze of locks, lists,\n  and subtle differences between how different notification systems\n  handle notification marks :( I'll think about it over night\"\n\nand after thinking about it, Jan says:\n\n \"OK, I have looked into the code some more and I found another\n  relatively simple way of fixing the original oops.  It will be IMHO\n  better than trying to fixup this issue which has more potential for\n  breakage.  I'll ask Linus to revert the fsnotify fix he already merged\n  and send a new fix\"\n\nReported-by: Kinglong Mee <kinglongmee@gmail.com>\nRequested-by: Jan Kara <jack@suse.cz>\nCc: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/RobertCNelson/ti-linux-kernel/commits/d725e66c06ab440032f49ef17e960896d0ec6d49"}]}