devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: kieran.bingham@ideasonboard.com
Cc: "Michal Vokáč" <michal.vokac@ysoft.com>,
	mchehab@kernel.org, linux-media@vger.kernel.org,
	"Rob Herring" <robh+dt@kernel.org>,
	"Mark Rutland" <mark.rutland@arm.com>,
	linux-renesas-soc@vger.kernel.org,
	"Kieran Bingham" <kieran.bingham+renesas@ideasonboard.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: dt: adv7604: Fix slave map documentation
Date: Wed, 08 Aug 2018 13:25:53 +0300	[thread overview]
Message-ID: <5273911.bCJl0SVgzf@avalon> (raw)
In-Reply-To: <b5b25641-f898-577b-7762-d72dd64272cf@ideasonboard.com>

Hi Kieran,

On Wednesday, 8 August 2018 13:23:32 EEST Kieran Bingham wrote:
> Hi Michal,
> 
> Thank you for your review.
> 
> +Rob, +Mark, +Laurent asking for opinions if anyone has any on prefixes
> through media tree.
> 
> On 08/08/18 08:48, Michal Vokáč wrote:
> > On 7.8.2018 17:54, Kieran Bingham wrote:
> > Hi Kieran,
> > 
> >> The reg-names property in the documentation is missing an '='. Add it.
> >> 
> >> Fixes: 9feb786876c7 ("media: dt-bindings: media: adv7604: Extend
> >> bindings to allow specifying slave map addresses")
> > 
> > "dt-bindings: media: " is preferred for the subject.
> 
> This patch will go through the media-tree as far as I am aware, and
> Mauro prefixes all commits through the media tree with "media:" if they
> are not already prefixed.
> 
> Thus this would then become "media: dt-bindings: media: adv7604: ...."
> as per my commit: 9feb786876c7 which seems a bit redundant.
> 
> Is it still desired ? If so I'll send a V2. (perhaps needed anyway, as I
> seem to have erroneously shortened dt-bindings: to just dt: which wasn't
> intentional.
> 
> > I think you should also add device tree maintainers to the recipients.
> 
> Added to this mail to ask opinions on patch prefixes above.
> 
> Originally, I believed the list was sufficient as this is a trivial
> patch, and it goes through the media tree.
> 
> But, it turned out to be more controversial :)
> 
> Rob, Mark, should I add you to all patches affecting DT? Or is the list
> sufficient?

Given the insane amount of patches received by DT maintainers, I personally 
try to use common sense and only disturb them when needed. Such a typo fix 
doesn't qualify for a full CC list in my opinion.

> >> Signed-off-by: Kieran Bingham <kieran.bingham@ideasonboard.com>
> >> ---
> >>   Documentation/devicetree/bindings/media/i2c/adv7604.txt | 2 +-
> >>   1 file changed, 1 insertion(+), 1 deletion(-)
> >> 
> >> diff --git a/Documentation/devicetree/bindings/media/i2c/adv7604.txt
> >> b/Documentation/devicetree/bindings/media/i2c/adv7604.txt
> >> index dcf57e7c60eb..b3e688b77a38 100644
> >> --- a/Documentation/devicetree/bindings/media/i2c/adv7604.txt
> >> +++ b/Documentation/devicetree/bindings/media/i2c/adv7604.txt
> >> @@ -66,7 +66,7 @@ Example:
> >>            * other maps will retain their default addresses.
> >>            */
> >>           reg = <0x4c>, <0x66>;
> >> -        reg-names "main", "edid";
> >> +        reg-names = "main", "edid";
> >>             reset-gpios = <&ioexp 0 GPIO_ACTIVE_LOW>;
> >>           hpd-gpios = <&ioexp 2 GPIO_ACTIVE_HIGH>;

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2018-08-08 10:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-07 15:54 [PATCH] media: dt: adv7604: Fix slave map documentation Kieran Bingham
2018-08-08  7:48 ` Michal Vokáč
2018-08-08 10:23   ` Kieran Bingham
2018-08-08 10:25     ` Laurent Pinchart [this message]
2018-08-08 12:33       ` Michal Vokáč
2018-08-08 12:51         ` 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=5273911.bCJl0SVgzf@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kieran.bingham+renesas@ideasonboard.com \
    --cc=kieran.bingham@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mchehab@kernel.org \
    --cc=michal.vokac@ysoft.com \
    --cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).