{"push_id":2844221403,"size":7,"distinct_size":7,"ref":"refs/heads/op6","head":"a227427c6c058aeb2f387e47d4798f2ed0e26dc2","before":"15c77354f5c6d4122378e1fad5a7b2b8f6454b4d","commits":[{"sha":"546810a881b3b72cc6bfa792b91a8352b0039553","author":{"name":"Miao Zhong","email":"bb30b99983adf9bbf072084414740747b43de602@hisilicon.com"},"message":"iommu/arm-smmu-v3: sync the OVACKFLG to PRIQ consumer register\n\nWhen PRI queue occurs overflow, driver should update the OVACKFLG to\nthe PRIQ consumer register, otherwise subsequent PRI requests will not\nbe processed.\n\nCc: Will Deacon <will.deacon@arm.com>\nCc: Robin Murphy <robin.murphy@arm.com>\nSigned-off-by: Miao Zhong <zhongmiao@hisilicon.com>\nSigned-off-by: Will Deacon <will.deacon@arm.com>","distinct":true,"url":"https://api.github.com/repos/hohoxu/n5kernel/commits/546810a881b3b72cc6bfa792b91a8352b0039553"},{"sha":"f51780409dfb1f8010658d93c19e89298f121f60","author":{"name":"Rajan Vaja","email":"958387e48e282671f29716c1b482329c5293cdb8@xilinx.com"},"message":"clk: clk-fixed-factor: Clear OF_POPULATED flag in case of failure\n\nFixed factor clock has two initializations at of_clk_init() time\nand during platform driver probe. Before of_clk_init() call,\nnode is marked as populated and so its probe never gets called.\n\nDuring of_clk_init() fixed factor clock registration may fail if\nany of its parent clock is not registered. In this case, it doesn't\nget chance to retry registration from probe. Clear OF_POPULATED\nflag if fixed factor clock registration fails so that clock\nregistration is attempted again from probe.\n\nSigned-off-by: Rajan Vaja <rajan.vaja@xilinx.com>\nSigned-off-by: Stephen Boyd <sboyd@kernel.org>","distinct":true,"url":"https://api.github.com/repos/hohoxu/n5kernel/commits/f51780409dfb1f8010658d93c19e89298f121f60"},{"sha":"6d281f9b94d5e239997ff3e6ffe04e4e61f59b3c","author":{"name":"Fredrik Noring","email":"dd9b4d0e439482ae9d9003873f12b3227dc66a21@nocrew.org"},"message":"fbdev: Distinguish between interlaced and progressive modes\n\nI discovered the problem when developing a frame buffer driver for the\nPlayStation 2 (not yet merged), using the following video modes for the\nPlayStation 3 in drivers/video/fbdev/ps3fb.c:\n\n    }, {\n        /* 1080if */\n        \"1080if\", 50, 1920, 1080, 13468, 148, 484, 36, 4, 88, 5,\n        FB_SYNC_BROADCAST, FB_VMODE_INTERLACED\n    }, {\n        /* 1080pf */\n        \"1080pf\", 50, 1920, 1080, 6734, 148, 484, 36, 4, 88, 5,\n        FB_SYNC_BROADCAST, FB_VMODE_NONINTERLACED\n    },\n\nIn ps3fb_probe, the mode_option module parameter is used with fb_find_mode\nbut it can only select the interlaced variant of 1920x1080 since the loop\nmatching the modes does not take the difference between interlaced and\nprogressive modes into account.\n\nIn short, without the patch, progressive 1920x1080 cannot be chosen as a\nmode_option parameter since fb_find_mode (falsely) thinks interlace is a\nperfect match.\n\nSigned-off-by: Fredrik Noring <noring@nocrew.org>\nCc: \"Maciej W. Rozycki\" <macro@linux-mips.org>\n[b.zolnierkie: updated patch description]\nSigned-off-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>","distinct":true,"url":"https://api.github.com/repos/hohoxu/n5kernel/commits/6d281f9b94d5e239997ff3e6ffe04e4e61f59b3c"},{"sha":"f8bf5b18a9770bf17d5850473bb9543c7b986216","author":{"name":"Hans Verkuil","email":"f625be9dbdcbbd12a043857af148e8fb895d9a1d@xs4all.nl"},"message":"media: videobuf2-core: check for q->error in vb2_core_qbuf()\n\n[ Upstream commit b509d733d337417bcb7fa4a35be3b9a49332b724 ]\n\nThe vb2_core_qbuf() function didn't check if q->error was set. It is\nchecked in __buf_prepare(), but that function isn't called if the buffer\nwas already prepared before with VIDIOC_PREPARE_BUF.\n\nSo check it at the start of vb2_core_qbuf() as well.\n\nSigned-off-by: Hans Verkuil <hans.verkuil@cisco.com>\nAcked-by: Sakari Ailus <sakari.ailus@linux.intel.com>\nSigned-off-by: Hans Verkuil <hans.verkuil@cisco.com>\nSigned-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>\nSigned-off-by: Sasha Levin <alexander.levin@microsoft.com>","distinct":true,"url":"https://api.github.com/repos/hohoxu/n5kernel/commits/f8bf5b18a9770bf17d5850473bb9543c7b986216"},{"sha":"531548bc5d7b194a43202eca3bd162a552da46f2","author":{"name":"Piotr Sawicki","email":"bb0def6f83384625f330e6577eeca5ecfb983316@partner.samsung.com"},"message":"Smack: Fix handling of IPv4 traffic received by PF_INET6 sockets\n\nA socket which has sk_family set to PF_INET6 is able to receive not\nonly IPv6 but also IPv4 traffic (IPv4-mapped IPv6 addresses).\n\nPrior to this patch, the smk_skb_to_addr_ipv6() could have been\ncalled for socket buffers containing IPv4 packets, in result such\ntraffic was allowed.\n\nSigned-off-by: Piotr Sawicki <p.sawicki2@partner.samsung.com>\nSigned-off-by: Casey Schaufler <casey@schaufler-ca.com>","distinct":true,"url":"https://api.github.com/repos/hohoxu/n5kernel/commits/531548bc5d7b194a43202eca3bd162a552da46f2"},{"sha":"792b3c65b76e5a06cfa8d98d2a1c79d73852cf26","author":{"name":"Mark Rutland","email":"1db9dd262beaa64f35756dd39531d9747b7778bb@arm.com"},"message":"arm64: fix possible spectre-v1 write in ptrace_hbp_set_event()\n\nIt's possible for userspace to control idx. Sanitize idx when using it\nas an array index, to inhibit the potential spectre-v1 write gadget.\n\nFound by smatch.\n\nSigned-off-by: Mark Rutland <mark.rutland@arm.com>\nCc: Catalin Marinas <catalin.marinas@arm.com>\nCc: Will Deacon <will.deacon@arm.com>\nSigned-off-by: Will Deacon <will.deacon@arm.com>","distinct":true,"url":"https://api.github.com/repos/hohoxu/n5kernel/commits/792b3c65b76e5a06cfa8d98d2a1c79d73852cf26"},{"sha":"a227427c6c058aeb2f387e47d4798f2ed0e26dc2","author":{"name":"Pingfan Liu","email":"8b7ae235fc8c4bcb9c310b7e5552a46fa4421ee1@gmail.com"},"message":"drivers/base: stop new probing during shutdown\n\nThere is a race window in device_shutdown(), which may cause\n-1. parent device shut down before child or\n-2. no shutdown on a new probing device.\n\nFor 1st, taking the following scenario:\n         device_shutdown                        new plugin device\n  list_del_init(parent_dev);\n  spin_unlock(list_lock);\n                                                  device_add(child)\n                                                  probe child\n  shutdown parent_dev\n       --> now child is on the tail of devices_kset\n\nFor 2nd, taking the following scenario:\n         device_shutdown                        new plugin device\n                                                  device_add(dev)\n  device_lock(dev);\n  ...\n  device_unlock(dev);\n                                                  probe dev\n       --> now, the new occurred dev has no opportunity to shutdown\n\nTo fix this race issue, just prevent the new probing request. With this\nlogic, device_shutdown() is more similar to dpm_prepare().\n\nSigned-off-by: Pingfan Liu <kernelfans@gmail.com>\nReviewed-by: Rafael J. Wysocki <rafael@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/hohoxu/n5kernel/commits/a227427c6c058aeb2f387e47d4798f2ed0e26dc2"}]}
{"actor":{"display_login":"hohoxu"}}