From: Mark Brown <broonie@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Biju Das <biju.das@bp.renesas.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
Chris Paterson <chris.paterson2@renesas.com>,
Fabrizio Castro <fabrizio.castro@bp.renesas.com>,
ALSA Development Mailing List <alsa-devel@alsa-project.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: ASoC: rsnd: Add device tree support for r8a774[35]
Date: Wed, 13 Dec 2017 12:55:31 +0000 [thread overview]
Message-ID: <20171213125531.GJ6416@sirena.org.uk> (raw)
In-Reply-To: <CAMuHMdVY5PwEvZYBzC_f-W_n9ATST4_tfPBO4CakYo-93DvLtA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 900 bytes --]
On Wed, Dec 13, 2017 at 01:34:40PM +0100, Geert Uytterhoeven wrote:
> The confusing part here is that for most[*] subsystems, patches touching
> only DT bindings should have a "dt-bindings" prefix, while patches touching
> both DT bindings and driver code should have the drivers' subsystem prefix.
> [*] I think you're about the only maintainer who insists on patches touching
> only DT bindings having the drivers' subsystem prefix, which people tend to
> forget, if they're even aware of that rule...
> Can we improve this?
This is something Rob's been pushing which seems like a step back to me
so I've been pushing back on it - it's causing problems for me spotting
things I need to look at and later on in review (including my scripting,
which does pay attention to subject lines). I suspect I'm at the upper
end of people getting lots of irrelevant stuff in copy which doesn't
help here.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 484 bytes --]
next prev parent reply other threads:[~2017-12-13 12:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 18:09 [PATCH] dt-bindings: ASoC: rsnd: Add device tree support for r8a774[35] Biju Das
2017-12-13 10:16 ` Geert Uytterhoeven
2017-12-13 12:20 ` Mark Brown
2017-12-13 12:34 ` Geert Uytterhoeven
2017-12-13 12:55 ` Mark Brown [this message]
2017-12-13 13:14 ` Biju Das
2017-12-13 13:35 ` [PATCH v2] " Biju Das
2017-12-13 13:45 ` Geert Uytterhoeven
2017-12-13 15:46 ` Applied "ASoC: rsnd: Add device tree support for r8a774[35]" to the asoc tree Mark Brown
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=20171213125531.GJ6416@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=biju.das@bp.renesas.com \
--cc=chris.paterson2@renesas.com \
--cc=fabrizio.castro@bp.renesas.com \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=lgirdwood@gmail.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.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