From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: Kieran Bingham <kbingham@kernel.org>,
linux-media@vger.kernel.org, laurent.pinchart@ideasonboard.com,
niklas.soderlund@ragnatech.se, linux-renesas-soc@vger.kernel.org,
kieran.bingham@ideasonboard.com,
Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
Subject: Re: [PATCH v4] v4l: subdev: tolerate null in media_entity_to_v4l2_subdev
Date: Thu, 8 Jun 2017 17:10:43 -0300 [thread overview]
Message-ID: <20170608171043.73dd28aa@vento.lan> (raw)
In-Reply-To: <20170608193210.GJ1019@valkosipuli.retiisi.org.uk>
Em Thu, 8 Jun 2017 22:32:10 +0300
Sakari Ailus <sakari.ailus@iki.fi> escreveu:
> Hi Mauro,
>
> On Thu, Jun 08, 2017 at 03:00:22PM -0300, Mauro Carvalho Chehab wrote:
> > Em Wed, 7 Jun 2017 10:52:07 +0100
> > Kieran Bingham <kbingham@kernel.org> escreveu:
> >
> > > From: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
> > >
> > > Return NULL, if a null entity is parsed for it's v4l2_subdev
> > >
> > > Signed-off-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
> >
> > Could you please improve this patch description?
> >
> > I'm unsure if this is a bug fix, or some sort of feature...
> >
> > On what situations would a null entity be passed to this function?
>
> I actually proposed this patch. This change is simply for convenience ---
> the caller doesn't need to make sure the subdev is non-NULL, possibly
> obtained from e.g. media_entity_remote_pad() which returns NULL all links to
> the pad are disabled. This is a recurring pattern, and making this change
> avoids an additional check.
>
> Having something along these lines in the patch description wouldn't hurt.
Patch added, with a description based on the above.
Thanks!
Mauro
next prev parent reply other threads:[~2017-06-08 20:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 9:52 [PATCH v4] v4l: subdev: tolerate null in media_entity_to_v4l2_subdev Kieran Bingham
2017-06-07 11:16 ` Sakari Ailus
2017-06-08 18:00 ` Mauro Carvalho Chehab
2017-06-08 19:32 ` Sakari Ailus
2017-06-08 20:10 ` Mauro Carvalho Chehab [this message]
2017-06-09 10:03 ` Kieran Bingham
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=20170608171043.73dd28aa@vento.lan \
--to=mchehab@s-opensource.com \
--cc=kbingham@kernel.org \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=niklas.soderlund@ragnatech.se \
--cc=sakari.ailus@iki.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.