linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Brian Masney <masneyb@onstation.org>,
	andy.gross@linaro.org, david.brown@linaro.org,
	devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-pwm@vger.kernel.org,
	linux-soc@vger.kernel.org, mark.rutland@arm.com,
	robh+dt@kernel.org, thierry.reding@gmail.com
Cc: masneyb@onstation.org, jonathan@marek.ca, ctatlor97@gmail.com
Subject: Re: [PATCH v2 0/3] treewide: add vibrator support for various MSM SOCs
Date: Mon, 15 Oct 2018 17:52:49 -0700	[thread overview]
Message-ID: <153965116919.5275.18169434559839796065@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20180926235112.25710-1-masneyb@onstation.org>

Quoting Brian Masney (2018-09-26 16:51:09)
> This patch set adds support for the vibrator found on various Qualcomm
> MSM SOCs. This is based on work from:

Can you please stop adding 'treewide:' to your cover letters? It is very
confusing while reading over subject summaries to see something that
isn't actually treewide end up being qcom specific.


      parent reply	other threads:[~2018-10-16  0:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-26 23:51 [PATCH v2 0/3] treewide: add vibrator support for various MSM SOCs Brian Masney
2018-09-26 23:51 ` [PATCH v2 1/3] dt-bindings: pwm: msm-vibrator: new bindings for MSM vibrator PWM Brian Masney
2018-09-26 23:51 ` [PATCH v2 2/3] pwm: msm-vibrator: new driver for the vibrator found on various MSM SOCs Brian Masney
2018-09-26 23:51 ` [PATCH v2 3/3] ARM: dts: qcom: msm8974-hammerhead: add device tree bindings for vibrator Brian Masney
2018-10-12 11:47 ` [PATCH v2 0/3] treewide: add vibrator support for various MSM SOCs Thierry Reding
2018-10-16  0:52 ` Stephen Boyd [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=153965116919.5275.18169434559839796065@swboyd.mtv.corp.google.com \
    --to=sboyd@kernel.org \
    --cc=andy.gross@linaro.org \
    --cc=ctatlor97@gmail.com \
    --cc=david.brown@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathan@marek.ca \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=linux-soc@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=masneyb@onstation.org \
    --cc=robh+dt@kernel.org \
    --cc=thierry.reding@gmail.com \
    /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).