From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-media@vger.kernel.org, niklas.soderlund@ragnatech.se
Subject: Re: [PATCH v2 5/9] media: Use single quotes to quote entity names
Date: Fri, 09 Dec 2016 17:19:46 +0200 [thread overview]
Message-ID: <2728859.u4HyMZ8Mmz@avalon> (raw)
In-Reply-To: <1481295222-14743-6-git-send-email-sakari.ailus@linux.intel.com>
Hi Sakari,
Thank you for the patch.
On Friday 09 Dec 2016 16:53:38 Sakari Ailus wrote:
> Instead of double quotes, use single quotes to quote entity names. Using
> single quotes is consistent with the English language and is also in line
> with the practices across the kernel.
>
> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> ---
> drivers/media/media-entity.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/media/media-entity.c b/drivers/media/media-entity.c
> index 1de28ce..5064ba0 100644
> --- a/drivers/media/media-entity.c
> +++ b/drivers/media/media-entity.c
> @@ -444,7 +444,7 @@ __must_check int __media_pipeline_start(struct
> media_entity *entity, ret = entity->ops->link_validate(link);
> if (ret < 0 && ret != -ENOIOCTLCMD) {
> dev_dbg(entity->graph_obj.mdev->dev,
> - "link validation failed for \"%s\":%u
-> \"%s\":%u, error %d\n",
> + "link validation failed for '%s':%u ->
'%s':%u, error %d\n",
> link->source->entity->name,
> link->source->index,
> entity->name, link->sink->index, ret);
> @@ -458,7 +458,7 @@ __must_check int __media_pipeline_start(struct
> media_entity *entity, if (!bitmap_full(active, entity->num_pads)) {
> ret = -ENOLINK;
> dev_dbg(entity->graph_obj.mdev->dev,
> - "\"%s\":%u must be connected by an enabled
link\n",
> + "'%s':%u must be connected by an enabled
link\n",
> entity->name,
> (unsigned)find_first_zero_bit(
> active, entity->num_pads));
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2016-12-09 15:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-09 14:53 [PATCH v2] Media pipeline and graph walk cleanups and fixes Sakari Ailus
2016-12-09 14:53 ` [PATCH v2 1/9] media: entity: Fix stream count check Sakari Ailus
2016-12-09 14:53 ` [PATCH v2 2/9] media: entity: Be vocal about failing sanity checks Sakari Ailus
2016-12-09 14:53 ` [PATCH v2 3/9] media: Rename graph and pipeline structs and functions Sakari Ailus
2016-12-09 14:53 ` [PATCH v2 4/9] media: entity: Split graph walk iteration into two functions Sakari Ailus
2016-12-09 14:53 ` [PATCH v2 5/9] media: Use single quotes to quote entity names Sakari Ailus
2016-12-09 15:19 ` Laurent Pinchart [this message]
2016-12-09 14:53 ` [PATCH v2 6/9] media: entity: Add debug information to graph walk Sakari Ailus
2016-12-09 14:53 ` [PATCH v2 7/9] omap3isp: Use a local media device pointer instead Sakari Ailus
2016-12-09 15:20 ` Laurent Pinchart
2016-12-09 14:53 ` [PATCH v2 8/9] xilinx: " Sakari Ailus
2016-12-09 15:21 ` Laurent Pinchart
2016-12-09 14:53 ` [PATCH v2 9/9] davinci: " Sakari Ailus
2016-12-09 15:21 ` Laurent Pinchart
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=2728859.u4HyMZ8Mmz@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=niklas.soderlund@ragnatech.se \
--cc=sakari.ailus@linux.intel.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;
as well as URLs for NNTP newsgroup(s).