mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shuah Khan <shuahkh@osg.samsung.com>
To: Marian Mihailescu <marian.mihailescu@adelaide.edu.au>
Cc: Andrzej Hajda <a.hajda@samsung.com>,
	Kyungmin Park <kyungmin.park@samsung.com>,
	kamil@wypas.org, jtp.park@samsung.com, mchehab@kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	linux-kernel@vger.kernel.org,
	Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [PATCH 2/2] media: s5p-mfc: fix lock confection - request_firmware() once and keep state
Date: Fri, 3 Nov 2017 08:09:00 -0600	[thread overview]
Message-ID: <f7839fdb-42e5-489d-26be-e3b1b9610aff@osg.samsung.com> (raw)
In-Reply-To: <CAM3PiRxjO-sP22v5ZSRvKUCwn7B8S_G_GVWW_Uk75aZd3CsoMQ@mail.gmail.com>

On 11/02/2017 06:43 PM, Marian Mihailescu wrote:
> I can confirm, with this patch, there is always error loading MFC in
> boot log, since FS is not mounted.
> 
> -Marian
> 

Please refrain from top posting to a kernel email threads. It is very difficult
to follow. Bottom post is the norm.

thanks,
-- Shuah 

  reply	other threads:[~2017-11-03 14:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-06 21:30 [PATCH 0/2] Fix s5p-mfc lock contention in request firmware paths 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 [this message]
2017-10-25 21:24 ` [PATCH 0/2] Fix s5p-mfc lock contention in request firmware paths Shuah Khan
2017-10-25 22:28   ` 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=f7839fdb-42e5-489d-26be-e3b1b9610aff@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=marian.mihailescu@adelaide.edu.au \
    --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®