All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Dybcio <konradybcio@gmail.com>
To: Bjorn Andersson <bjorn.andersson@linaro.org>,
	Andy Gross <agross@kernel.org>
Cc: "Pavel Machek" <pavel@ucw.cz>, "Dan Murphy" <dmurphy@ti.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Thierry Reding" <thierry.reding@gmail.com>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Lee Jones" <lee.jones@linaro.org>,
	"Martin Botka" <martin.botka1@gmail.com>,
	linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-pwm@vger.kernel.org
Subject: Re: [PATCH v4 3/4] arm64: dts: qcom: msm8996: Add mpp and lpg blocks
Date: Thu, 1 Oct 2020 17:22:13 +0200	[thread overview]
Message-ID: <424f7b71-fb7e-fb45-c449-987ec3578290@gmail.com> (raw)
In-Reply-To: <20200929031544.1000204-4-bjorn.andersson@linaro.org>

Hi, 

Just a nitpick: the title says "qcom: msm8996", whereas the file being changed is pm(i)8994.dtsi. This also applies to most msm8992/94 platforms, as the PMIC was used there too.

Konrad

  reply	other threads:[~2020-10-01 15:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-29  3:15 [PATCH v4 0/4] Qualcomm Light Pulse Generator Bjorn Andersson
2020-09-29  3:15 ` [PATCH v4 1/4] dt-bindings: leds: Add Qualcomm Light Pulse Generator binding Bjorn Andersson
2020-09-29 14:48   ` Rob Herring
2020-09-29 14:51   ` Rob Herring
2020-09-29  3:15 ` [PATCH v4 2/4] leds: Add driver for Qualcomm LPG Bjorn Andersson
2020-09-29  5:09   ` kernel test robot
2020-09-29  5:09     ` kernel test robot
2020-10-07  9:40   ` Luca Weiss
2020-09-29  3:15 ` [PATCH v4 3/4] arm64: dts: qcom: msm8996: Add mpp and lpg blocks Bjorn Andersson
2020-10-01 15:22   ` Konrad Dybcio [this message]
2020-10-01 16:21     ` Bjorn Andersson
2020-09-29  3:15 ` [PATCH v4 4/4] arm64: dts: qcom: Add user LEDs on db820c Bjorn Andersson

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=424f7b71-fb7e-fb45-c449-987ec3578290@gmail.com \
    --to=konradybcio@gmail.com \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmurphy@ti.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=martin.botka1@gmail.com \
    --cc=pavel@ucw.cz \
    --cc=robh+dt@kernel.org \
    --cc=thierry.reding@gmail.com \
    --cc=u.kleine-koenig@pengutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.