From: Shuah Khan <shuahkh@osg.samsung.com>
To: kyungmin.park@samsung.com, kamil@wypas.org, jtp.park@samsung.com,
a.hajda@samsung.com, mchehab@kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [PATCH 0/2] Fix s5p-mfc lock contention in request firmware paths
Date: Wed, 25 Oct 2017 15:24:57 -0600 [thread overview]
Message-ID: <354e3c31-e502-5ba6-d705-9d67764e78bf@osg.samsung.com> (raw)
In-Reply-To: <cover.1507325072.git.shuahkh@osg.samsung.com>
On 10/06/2017 03:30 PM, Shuah Khan wrote:
> This patch series fixes inefficiencies and lock contention in the request
> firmware paths.
>
> Shuah Khan (2):
> media: s5p-mfc: check for firmware allocation before requesting
> firmware
> media: s5p-mfc: fix lock confection - request_firmware() once and keep
> state
>
> drivers/media/platform/s5p-mfc/s5p_mfc.c | 4 ++++
> drivers/media/platform/s5p-mfc/s5p_mfc_common.h | 3 +++
> drivers/media/platform/s5p-mfc/s5p_mfc_ctrl.c | 15 ++++++++++-----
> 3 files changed, 17 insertions(+), 5 deletions(-)
>
Any feedback on this series?
thanks,
-- Shuah
next prev parent reply other threads:[~2017-10-25 21:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 21:30 Shuah Khan
2017-10-06 21:30 ` [PATCH 1/2] media: s5p-mfc: check for firmware allocation before requesting firmware Shuah Khan
2017-11-02 8:12 ` Andrzej Hajda
2017-11-03 0:23 ` Shuah Khan
2017-10-06 21:30 ` [PATCH 2/2] media: s5p-mfc: fix lock confection - request_firmware() once and keep state Shuah Khan
2017-11-02 8:31 ` Andrzej Hajda
2017-11-03 0:27 ` Shuah Khan
2017-11-03 0:43 ` Marian Mihailescu
2017-11-03 14:09 ` Shuah Khan
2017-10-25 21:24 ` Shuah Khan [this message]
2017-10-25 22:28 ` [PATCH 0/2] Fix s5p-mfc lock contention in request firmware paths Marian Mihailescu
2017-10-26 6:53 ` Shuah Khan
2017-10-30 21:51 ` Shuah Khan
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=354e3c31-e502-5ba6-d705-9d67764e78bf@osg.samsung.com \
--to=shuahkh@osg.samsung.com \
--cc=a.hajda@samsung.com \
--cc=jtp.park@samsung.com \
--cc=kamil@wypas.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@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
all inboxes | Powered by JetHome®