Re: [PATCH V2 linux-next] staging: media: atomisp: kmap() can't fail

2017-04-26 Thread Alan Cox
On Wed, 2017-04-26 at 20:44 +0200, Fabian Frederick wrote: > There's no need to check kmap() return value because it won't fail. > If it's highmem mapping, it will receive virtual address > or a new one; if it's lowmem, all kernel pages are already being > mapped. > > (Thanks to Jan Kara for

Re: [PATCH V2 linux-next] staging: media: atomisp: kmap() can't fail

2017-04-26 Thread Alan Cox
On Wed, 2017-04-26 at 20:44 +0200, Fabian Frederick wrote: > There's no need to check kmap() return value because it won't fail. > If it's highmem mapping, it will receive virtual address > or a new one; if it's lowmem, all kernel pages are already being > mapped. > > (Thanks to Jan Kara for

[PATCH V2 linux-next] staging: media: atomisp: kmap() can't fail

2017-04-26 Thread Fabian Frederick
There's no need to check kmap() return value because it won't fail. If it's highmem mapping, it will receive virtual address or a new one; if it's lowmem, all kernel pages are already being mapped. (Thanks to Jan Kara for explanations) Signed-off-by: Fabian Frederick --- V2:

[PATCH V2 linux-next] staging: media: atomisp: kmap() can't fail

2017-04-26 Thread Fabian Frederick
There's no need to check kmap() return value because it won't fail. If it's highmem mapping, it will receive virtual address or a new one; if it's lowmem, all kernel pages are already being mapped. (Thanks to Jan Kara for explanations) Signed-off-by: Fabian Frederick --- V2: Verbose description