Applied. Thanks! Alex On Tue, Feb 9, 2021 at 7:50 AM Christian König <christian.koenig@xxxxxxx> wrote: > > Reviewed-by: Christian König <christian.koenig@xxxxxxx> for the series. > > Am 09.02.21 um 13:44 schrieb Sebastian Andrzej Siewior: > > Folks, > > > > in the discussion about preempt count consistency across kernel > > configurations: > > > > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flore.kernel.org%2Fr%2F20200914204209.256266093%40linutronix.de%2F&data=04%7C01%7Cchristian.koenig%40amd.com%7C66cfb449f0ba475dd76b08d8ccf87a85%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637484714876862283%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=g04sQoqvfkuHzplig%2F%2BOruqzmyypIhaqrkKU0xeIJ80%3D&reserved=0 > > > > it was concluded that the usage of in_interrupt() and related context > > checks should be removed from non-core code. > > > > In the long run, usage of 'preemptible, in_*irq etc.' should be banned from > > driver code completely. > > > > This series addresses parts of the amdgpu driver. There are still call sites > > left in in the amdgpu driver. > > > > v1…v2: > > - Limit to admgpu only > > - use "bool" instead of "bool == true" > > > > Sebastian > > > > > > _______________________________________________ > amd-gfx mailing list > amd-gfx@xxxxxxxxxxxxxxxxxxxxx > https://lists.freedesktop.org/mailman/listinfo/amd-gfx _______________________________________________ amd-gfx mailing list amd-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/amd-gfx
