From: Doug Anderson <dianders@chromium.org>
To: Dilip Kota <dkota@codeaurora.org>
Cc: timur@codeaurora.org, Stephen Boyd <swboyd@chromium.org>,
Mark Brown <broonie@kernel.org>,
Matthias Kaehlcke <mka@chromium.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH V2] Add SPI driver support for GENI based QUP
Date: Fri, 20 Jul 2018 14:13:15 -0700 [thread overview]
Message-ID: <CAD=FV=Va2sr7AOvvo-Pw1ARaZyxzAGLK19qMG+PyNMpmAkV3Og@mail.gmail.com> (raw)
In-Reply-To: <1532087461-3474-1-git-send-email-dkota@codeaurora.org>
Hi,
On Fri, Jul 20, 2018 at 4:50 AM, Dilip Kota <dkota@codeaurora.org> wrote:
> This patch series adds SPI driver support for GENI based QUP.
> Also adding the device tree binding document for reference
> as per reviewers request which was merged in Linus tree.
>
> Girish Mahadevan (1):
> spi: spi-geni-qcom: Add SPI driver support for GENI based QUP
>
> drivers/spi/Kconfig | 12 +
> drivers/spi/Makefile | 1 +
> drivers/spi/spi-geni-qcom.c | 685 ++++++++++++++++++++++++++++++++++++++
> include/linux/spi/spi-geni-qcom.h | 14 +
> 4 files changed, 712 insertions(+)
> create mode 100644 drivers/spi/spi-geni-qcom.c
> create mode 100644 include/linux/spi/spi-geni-qcom.h
This looks like it was supposed to be a cover letter. Typically
that's labelled as "patch 0" in the series. Other handy traditions:
* The cover letter should contain a description of what changed
between this patch and the last one
* You only want a cover letter for a patch series with more than one
patch in it. In your case you only have one patch so you should have
no cover letter.
* It's handy if your cover letter has prefixes that match the
subsystem just like the patch itself. AKA: "spi: spi-geni-qcom:"
Personally I use "patman" to help me with sending out my patches. See
<https://github.com/u-boot/u-boot/tree/master/tools/patman>.
-Doug
prev parent reply other threads:[~2018-07-20 21:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 11:50 [PATCH V2] Add SPI driver support for GENI based QUP Dilip Kota
2018-07-20 11:50 ` [PATCH V2] spi: spi-geni-qcom: " Dilip Kota
2018-07-20 22:45 ` kbuild test robot
2018-07-20 22:53 ` Doug Anderson
2018-07-20 23:32 ` Doug Anderson
2018-07-20 23:37 ` kbuild test robot
2018-07-23 10:27 ` dkota
2018-07-20 11:51 ` [PATCH V2] dt-bindings: soc: qcom: Add device tree binding for GENI SE Dilip Kota
2018-07-20 20:35 ` Doug Anderson
2018-07-20 21:13 ` Doug Anderson [this message]
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='CAD=FV=Va2sr7AOvvo-Pw1ARaZyxzAGLK19qMG+PyNMpmAkV3Og@mail.gmail.com' \
--to=dianders@chromium.org \
--cc=broonie@kernel.org \
--cc=dkota@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@chromium.org \
--cc=swboyd@chromium.org \
--cc=timur@codeaurora.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).