From: Mark Brown <broonie@kernel.org>
To: Lubomir Rintel <lkundrak@v3.sk>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
James Cameron <quozl@laptop.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Eric Miao <eric.y.miao@gmail.com>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Daniel Mack <daniel@zonque.org>,
Robert Jarzmik <robert.jarzmik@free.fr>,
linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 01/11] dt-bindings: spi/spi-pxa2xx: add PXA2xx SSP SPI Controller
Date: Fri, 12 Oct 2018 19:00:02 +0200 [thread overview]
Message-ID: <20181012170002.GJ2340@sirena.org.uk> (raw)
In-Reply-To: <8cafa3f97fbe2a01ccf968b39469751b449e324b.camel@v3.sk>
[-- Attachment #1: Type: text/plain, Size: 1025 bytes --]
On Thu, Oct 11, 2018 at 07:59:15PM +0200, Lubomir Rintel wrote:
> On Thu, 2018-10-11 at 15:27 +0100, Mark Brown wrote:
> > Please use subject lines matching the style for the subsystem. This
> > makes it easier for people to identify relevant patches.
> Thanks for the response.
> I'm a little confused here. Why I chose this subject line is because I
> did this:
> git log --no-merges Documentation/devicetree/bindings/
Try Documentation/devicetree/bindings/spi instead :)
> to figure out what's the typical subject for the DT binding changes.
> I also believed that's the right way to get Rob Herring's and Mark
> Rutland's attention. Do the device tree binding documentation typically
There *is* some debate for the DT bindings unfortunately.
> go in with the associated drivers, or via their tree ("OPEN FIRMWARE
> AND FLATTENED DEVICE TREE BINDINGS" in MAINTIANERS)?
They usually go in with the drivers. This one isn't so bad since it
does mention SPI, it's a worse problem when that's not present at all.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-10-12 17:00 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 17:09 [PATCH 0/11] spi: pxa2xx: add DT and slave mode support Lubomir Rintel
2018-10-10 17:09 ` [PATCH v2 01/11] dt-bindings: spi/spi-pxa2xx: add PXA2xx SSP SPI Controller Lubomir Rintel
2018-10-11 14:27 ` Mark Brown
2018-10-11 17:59 ` Lubomir Rintel
2018-10-12 17:00 ` Mark Brown [this message]
2018-10-17 19:32 ` Rob Herring
2018-11-04 12:00 ` Pavel Machek
2018-10-10 17:09 ` [PATCH v2 02/11] PCI: Provide pci_match_id() with CONFIG_PCI=n Lubomir Rintel
2018-11-04 12:02 ` Pavel Machek
2018-10-10 17:09 ` [PATCH 03/11] spi: pxa2xx: Use an enum for type Lubomir Rintel
2018-11-04 12:03 ` Pavel Machek
2018-10-10 17:09 ` [PATCH 04/11] spi: pxa2xx: Add devicetree support Lubomir Rintel
2018-11-04 12:04 ` Pavel Machek
2018-10-10 17:09 ` [PATCH 05/11] DT: marvell,mmp2: Add SSP1 and SSP3 Lubomir Rintel
2018-10-29 5:35 ` James Cameron
2018-11-04 12:06 ` Pavel Machek
2018-10-10 17:09 ` [PATCH 06/11] dt-bindings: spi/spi-pxa2xx: Add spi-slave property Lubomir Rintel
2018-10-17 19:33 ` Rob Herring
2018-11-04 12:07 ` Pavel Machek
2018-10-10 17:09 ` [PATCH 07/11] spi: Deal with slaves that return from transfer_one() unfinished Lubomir Rintel
2018-10-11 7:23 ` Geert Uytterhoeven
2018-11-04 12:09 ` Pavel Machek
2018-10-10 17:09 ` [PATCH 08/11] spi: pxa2xx: Add slave mode support Lubomir Rintel
2018-11-04 12:12 ` Pavel Machek
2018-10-10 17:09 ` [PATCH 09/11] dt-bindings: spi/spi-pxa2xx: Add ready GPIO signal Lubomir Rintel
2018-10-11 7:26 ` Geert Uytterhoeven
2018-11-04 12:13 ` Pavel Machek
2018-10-10 17:09 ` [PATCH 10/11] spi: pxa2xx: Add ready signal Lubomir Rintel
2018-10-11 7:28 ` Geert Uytterhoeven
2018-10-11 16:13 ` Lubomir Rintel
2018-11-04 12:16 ` Pavel Machek
2018-10-10 17:09 ` [PATCH 11/11] spi: pxa2xx: Deal with the leftover garbage in TXFIFO Lubomir Rintel
2018-11-04 12:19 ` Pavel Machek
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=20181012170002.GJ2340@sirena.org.uk \
--to=broonie@kernel.org \
--cc=daniel@zonque.org \
--cc=devicetree@vger.kernel.org \
--cc=eric.y.miao@gmail.com \
--cc=geert+renesas@glider.be \
--cc=haojian.zhuang@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=mark.rutland@arm.com \
--cc=quozl@laptop.org \
--cc=robert.jarzmik@free.fr \
--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
Powered by JetHome