All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil@xs4all.nl>
To: Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
	Linux Media Mailing List <linux-media@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
	Kyungmin Park <kyungmin.park@samsung.com>,
	Sylwester Nawrocki <s.nawrocki@samsung.com>,
	Kukjin Kim <kgene@kernel.org>,
	Krzysztof Kozlowski <k.kozlowski@samsung.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Akihiro Tsukada <tskd08@gmail.com>,
	Tina Ruchandani <ruchandani.tina@gmail.com>,
	Antti Palosaari <crope@iki.fi>, Arnd Bergmann <arnd@arndb.de>,
	Dan Carpenter <dan.carpenter@oracle.com>,
	Hans Verkuil <hans.verkuil@cisco.com>,
	Prabhakar Lad <prabhakar.csengg@gmail.com>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Boris BREZILLON <boris.brezillon@free-electrons.com>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Markus Elfring <elfring@users.sourceforge.net>,
	linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: [PATCH RFC v3 10/16] media: rename link source/sink to pad0_source/pad1_sink
Date: Thu, 13 Aug 2015 09:58:16 +0200	[thread overview]
Message-ID: <55CC4E18.7080605@xs4all.nl> (raw)
In-Reply-To: <30472f0a7f52ee834978c70cbecc5c035ce20f71.1439410053.git.mchehab@osg.samsung.com>

On 08/12/15 22:14, Mauro Carvalho Chehab wrote:
> Change the internal namespace for links between two pads to
> have the "pad" there.
> 
> We're also numbering it, as a common constructor is to do
> things like:
> 
>  	if (link->port1.type != MEDIA_GRAPH_PAD)
>  		continue;
>  	if (link->pad1_sink->entity == entity)
> 		/* do something */
> 
> by preserving the number, we keep consistency between
> port1 and pad1_sink, and port0 and pad0_source.

I would really leave this patch out. As long as sink and source are consistently
used for pads (and they are), then I see no benefit at all to this change.

Another reason why I don't like this is that pad0_ and pad1_ are actually
confusing since they suggested to me when I first read it that pad0_ referred to
the pad with index 0 and pad1_ referred to the pad with index 1.

That's obviously not the case, but it does mean that the prefix doesn't really
make things clearer.

I would just stick with source and sink.

Regards,

	Hans

WARNING: multiple messages have this Message-ID (diff)
From: hverkuil@xs4all.nl (Hans Verkuil)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC v3 10/16] media: rename link source/sink to pad0_source/pad1_sink
Date: Thu, 13 Aug 2015 09:58:16 +0200	[thread overview]
Message-ID: <55CC4E18.7080605@xs4all.nl> (raw)
In-Reply-To: <30472f0a7f52ee834978c70cbecc5c035ce20f71.1439410053.git.mchehab@osg.samsung.com>

On 08/12/15 22:14, Mauro Carvalho Chehab wrote:
> Change the internal namespace for links between two pads to
> have the "pad" there.
> 
> We're also numbering it, as a common constructor is to do
> things like:
> 
>  	if (link->port1.type != MEDIA_GRAPH_PAD)
>  		continue;
>  	if (link->pad1_sink->entity == entity)
> 		/* do something */
> 
> by preserving the number, we keep consistency between
> port1 and pad1_sink, and port0 and pad0_source.

I would really leave this patch out. As long as sink and source are consistently
used for pads (and they are), then I see no benefit at all to this change.

Another reason why I don't like this is that pad0_ and pad1_ are actually
confusing since they suggested to me when I first read it that pad0_ referred to
the pad with index 0 and pad1_ referred to the pad with index 1.

That's obviously not the case, but it does mean that the prefix doesn't really
make things clearer.

I would just stick with source and sink.

Regards,

	Hans

  reply	other threads:[~2015-08-13  8:00 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-12 20:14 [PATCH RFC v3 00/16] Changes on MC core due to MC workshop discussion Mauro Carvalho Chehab
2015-08-12 20:14 ` [PATCH RFC v3 01/16] media: Add some fields to store graph objects Mauro Carvalho Chehab
2015-08-12 20:14 ` [PATCH RFC v3 02/16] media: Add a common embeed struct for all media " Mauro Carvalho Chehab
2015-08-14 13:08   ` Sakari Ailus
2015-08-14 13:21     ` Mauro Carvalho Chehab
2015-08-14 13:28       ` Hans Verkuil
2015-08-12 20:14 ` [PATCH RFC v3 03/16] media: add functions to inialize media_graph_obj Mauro Carvalho Chehab
2015-08-12 20:14 ` [PATCH RFC v3 04/16] media: ensure that entities will have an object ID Mauro Carvalho Chehab
2015-08-12 20:14 ` [PATCH RFC v3 05/16] media: initialize PAD objects Mauro Carvalho Chehab
2015-08-12 20:14 ` [PATCH RFC v3 06/16] media: initialize the graph object inside the media links Mauro Carvalho Chehab
2015-08-12 20:14 ` [PATCH RFC v3 07/16] media: get rid of unused "extra_links" param on media_entity_init() Mauro Carvalho Chehab
2015-08-12 20:14   ` Mauro Carvalho Chehab
2015-08-12 20:14   ` Mauro Carvalho Chehab
2015-08-12 20:14   ` Mauro Carvalho Chehab
2015-08-14 10:33   ` Sakari Ailus
2015-08-14 10:33     ` Sakari Ailus
2015-08-14 10:33     ` Sakari Ailus
2015-08-14 10:33     ` Sakari Ailus
2015-08-14 11:07     ` Mauro Carvalho Chehab
2015-08-14 11:07       ` Mauro Carvalho Chehab
2015-08-14 11:07       ` Mauro Carvalho Chehab
2015-08-14 11:07       ` Mauro Carvalho Chehab
2015-08-12 20:14 ` [PATCH RFC v3 08/16] media: convert links from array to list Mauro Carvalho Chehab
2015-08-12 20:14 ` [PATCH RFC v3 09/16] media: use media_graph_obj for link endpoints Mauro Carvalho Chehab
2015-08-12 20:14 ` [PATCH RFC v3 10/16] media: rename link source/sink to pad0_source/pad1_sink Mauro Carvalho Chehab
2015-08-12 20:14   ` Mauro Carvalho Chehab
2015-08-12 20:14   ` Mauro Carvalho Chehab
2015-08-13  7:58   ` Hans Verkuil [this message]
2015-08-13  7:58     ` Hans Verkuil
2015-08-12 20:14 ` [PATCH RFC v3 11/16] media: rename the function that create pad links Mauro Carvalho Chehab
2015-08-12 20:14   ` Mauro Carvalho Chehab
2015-08-12 20:14   ` Mauro Carvalho Chehab
2015-08-12 20:14   ` Mauro Carvalho Chehab
2015-08-12 20:14 ` [PATCH RFC v3 12/16] media: move __media_entity_remove_link to avoid prototype Mauro Carvalho Chehab
2015-08-12 20:14 ` [PATCH RFC v3 13/16] media: make the internal function to create links more generic Mauro Carvalho Chehab
2015-08-12 20:14 ` [PATCH RFC v3 14/16] media: add a generic function to remove a link Mauro Carvalho Chehab
2015-08-12 20:45   ` Shuah Khan
2015-08-12 20:52     ` Mauro Carvalho Chehab
2015-08-12 21:07       ` Shuah Khan
2015-08-12 20:14 ` [PATCH RFC v3 15/16] media: rename media_entity_remove_foo functions Mauro Carvalho Chehab
2015-08-12 20:15 ` [PATCH RFC v3 16/16] media: add functions to allow creating interfaces Mauro Carvalho Chehab

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=55CC4E18.7080605@xs4all.nl \
    --to=hverkuil@xs4all.nl \
    --cc=arnd@arndb.de \
    --cc=boris.brezillon@free-electrons.com \
    --cc=crope@iki.fi \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=elfring@users.sourceforge.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=hans.verkuil@cisco.com \
    --cc=k.kozlowski@samsung.com \
    --cc=kgene@kernel.org \
    --cc=kyungmin.park@samsung.com \
    --cc=lars@metafoo.de \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=mchehab@osg.samsung.com \
    --cc=prabhakar.csengg@gmail.com \
    --cc=ruchandani.tina@gmail.com \
    --cc=s.nawrocki@samsung.com \
    --cc=sakari.ailus@linux.intel.com \
    --cc=tskd08@gmail.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 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.