Displaying 4 results from an estimated 4 matches for "cahk".
Did you mean:
cah
2023 Mar 01
5
[PATCH 0/2] drm/nouveau: avoid usage of list iterator after loop
...correct 'nvkm_pstate'
structs.
That allows catching potential bugs with BUG_ON(!pstate) that otherwise
would be completely undetectable.
It also helps the greater mission to hopefully move the list iterator
variable into the iterating macro directly [1].
Link: https://lore.kernel.org/all/CAHk-=wgRr_D8CB-D9Kg-c=EHreAsk5SqXPwr9Y7k9sA6cWXJ6w at mail.gmail.com/ [1]
Signed-off-by: Jakob Koschel <jkl820.git at gmail.com>
---
Jakob Koschel (2):
drm/nouveau/device: avoid usage of list iterator after loop
drm/nouveau/clk: avoid usage of list iterator after loop
drivers/gpu/dr...
2023 Mar 07
1
[PATCH 0/2] drm/nouveau: avoid usage of list iterator after loop
...gt;
> That allows catching potential bugs with BUG_ON(!pstate) that otherwise
> would be completely undetectable.
>
> It also helps the greater mission to hopefully move the list iterator
> variable into the iterating macro directly [1].
>
> Link: https://lore.kernel.org/all/CAHk-=wgRr_D8CB-D9Kg-c=EHreAsk5SqXPwr9Y7k9sA6cWXJ6w at mail.gmail.com/ [1]
> Signed-off-by: Jakob Koschel <jkl820.git at gmail.com>
> ---
> Jakob Koschel (2):
> drm/nouveau/device: avoid usage of list iterator after loop
> drm/nouveau/clk: avoid usage of list iterator af...
2023 Mar 07
0
[PATCH 1/2] drm/nouveau/device: avoid usage of list iterator after loop
...al bugs.
>
> Additionally, Linus proposed to avoid any use of the list iterator
> variable after the loop, in the attempt to move the list iterator
> variable declaration into the marcro to avoid any potential misuse after
> the loop [1].
>
> Link: https://lore.kernel.org/all/CAHk-=wgRr_D8CB-D9Kg-c=EHreAsk5SqXPwr9Y7k9sA6cWXJ6w at mail.gmail.com/ [1]
> Signed-off-by: Jakob Koschel <jkl820.git at gmail.com>
> ---
> drivers/gpu/drm/nouveau/nvkm/engine/device/ctrl.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/driver...
2023 Feb 20
1
[PATCH drm-next v2 03/16] maple_tree: split up MA_STATE() macro
...this could occur.
>
> It is also worth pointing out that it would be much safer to use a
> function to do the above so you get type safety.. and I was asked to add
> this to the VMA interface by Linus [1], which is on its way upstream [2].
>
> 1. https://lore.kernel.org/linux-mm/CAHk-=wg9WQXBGkNdKD2bqocnN73rDswuWsavBB7T-tekykEn_A at mail.gmail.com/
> 2. https://lore.kernel.org/linux-mm/20230120162650.984577-1-Liam.Howlett at oracle.com/
You mean having wrappers like sample_find() instead of directly using
mas_find()?
>
>>
>> Signed-off-by: Danilo Krummrich...