From: Lubomir Rintel <lkundrak@v3.sk>
To: Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-spi@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v2 1/5] dt-bindings: spi/spi-pxa2xx: add PXA2xx SSP SPI Controller
Date: Tue, 18 Sep 2018 14:15:12 +0200 [thread overview]
Message-ID: <54f5d070c8b0615baa26983e97e2a22401973096.camel@v3.sk> (raw)
In-Reply-To: <20180917175753.GE2471@sirena.org.uk>
On Mon, 2018-09-17 at 10:57 -0700, Mark Brown wrote:
> On Mon, Sep 17, 2018 at 01:35:55PM +0200, Lubomir Rintel wrote:
> > This is the SPI controller found on Marvel MMP2 and perhaps more
> > platforms.
>
> I'm missing patches 2 and 5 from this series. What's going on with
> them, are there any dependencies?
Sorry, I was not sure how to Cc people properly. I haven't dealt with a
patchset that spanned multiple subsystems before.
I thought it might have been a good idea to add individual people
suggested by get_maintainer.pl in commits' "Cc:" tag, while passing the
lists to --cc argument of git send-email.
Should I've Cc'd everyone on the full series, even if only a patch or
two might be really interesting to them? How do I decide whether the
recipient needs to be in the commit's commit message (as opposed to
just --cc on a command line)?
https://lore.kernel.org/lkml/20180917113559.11101-1-lkundrak@v3.sk/
>
> > Changes since v1:
> > - s/ssp@d4035000/spi@d4035000/
>
> As covered in SubmittingPatches please put inter-version changelogs
> after the --- so they don't end up in the commits.
Will do. I was actually not sure about that, so I took a short look at
the git log, and it seemed to me that commit messages with the
changelogs are quite common.
Thanks you,
Lubo
next prev parent reply other threads:[~2018-09-18 12:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-17 11:35 [PATCH v2 0/5] Make SPI work on DT MMP2 Lubomir Rintel
2018-09-17 11:35 ` [PATCH v2 1/5] dt-bindings: spi/spi-pxa2xx: add PXA2xx SSP SPI Controller Lubomir Rintel
2018-09-17 17:57 ` Mark Brown
2018-09-18 12:15 ` Lubomir Rintel [this message]
2018-09-18 15:42 ` Mark Brown
2018-09-18 17:43 ` Mark Brown
2018-09-17 11:35 ` [PATCH v2 2/5] PCI: Provide pci_match_id() with CONFIG_PCI=n Lubomir Rintel
2018-09-17 11:35 ` [PATCH v2 3/5] spi: pxa2xx: Use an enum for type Lubomir Rintel
2018-09-17 11:35 ` [PATCH v2 4/5] spi: pxa2xx: Add devicetree support Lubomir Rintel
2018-09-17 11:35 ` [PATCH v2 5/5] DT: marvell,mmp2: Add SSP1 and SSP3 Lubomir Rintel
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=54f5d070c8b0615baa26983e97e2a22401973096.camel@v3.sk \
--to=lkundrak@v3.sk \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).