From: Steve Longerbeam <slongerbeam@gmail.com>
To: Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-media@vger.kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org,
Steve Longerbeam <steve_longerbeam@mentor.com>
Subject: Re: [PATCH] media: staging/imx: do not return error in link_notify for unknown sources
Date: Wed, 11 Oct 2017 15:14:26 -0700 [thread overview]
Message-ID: <87b48a34-4beb-eb21-3361-28f6edb6d73c@gmail.com> (raw)
In-Reply-To: <20171011214906.GX20805@n2100.armlinux.org.uk>
On 10/11/2017 02:49 PM, Russell King - ARM Linux wrote:
> On Tue, Oct 03, 2017 at 12:09:13PM -0700, Steve Longerbeam wrote:
>> imx_media_link_notify() should not return error if the source subdevice
>> is not recognized by imx-media, that isn't an error. If the subdev has
>> controls they will be inherited starting from a known subdev.
> What does "a known subdev" mean?
It refers to the previous sentence, "not recognized by imx-media". A
subdev that was not registered via async registration and so not in
imx-media's async subdev list. I could elaborate in the commit message
but it seems fairly obvious to me.
Steve
next prev parent reply other threads:[~2017-10-11 22:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 19:09 Steve Longerbeam
2017-10-11 21:49 ` Russell King - ARM Linux
2017-10-11 22:14 ` Steve Longerbeam [this message]
2017-10-11 23:06 ` Russell King - ARM Linux
2017-10-11 23:14 ` Steve Longerbeam
2017-10-11 23:27 ` Russell King - ARM Linux
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=87b48a34-4beb-eb21-3361-28f6edb6d73c@gmail.com \
--to=slongerbeam@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mchehab@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=steve_longerbeam@mentor.com \
/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®