From: Alan Cox <alan@linux.intel.com>
To: Fabian Frederick <fabf@skynet.be>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jan Kara <jack@suse.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 linux-next] staging: media: atomisp: kmap() can't fail
Date: Thu, 27 Apr 2017 00:02:41 +0100 [thread overview]
Message-ID: <1493247761.10302.129.camel@linux.intel.com> (raw)
In-Reply-To: <20170426184423.21301-1-fabf@skynet.be>
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 explanations)
>
Thanks - queued.
Alan
prev parent reply other threads:[~2017-04-26 23:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 18:44 [PATCH V2 linux-next] staging: media: atomisp: kmap() can't fail Fabian Frederick
2017-04-26 23:02 ` Alan Cox [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1493247761.10302.129.camel@linux.intel.com \
--to=alan@linux.intel.com \
--cc=fabf@skynet.be \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox