From: Stephen Boyd <swboyd@chromium.org>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Lee Jones <lee.jones@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
satya priya <skakit@codeaurora.org>
Cc: Das Srinagesh <gurus@codeaurora.org>,
kgunda@codeaurora.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH V7 0/3] Convert qcom pmic gpio bindings to YAML
Date: Mon, 26 Jul 2021 19:10:08 -0400 [thread overview]
Message-ID: <CAE-0n53bqJ8iBwBRwwf=-Fob5AObe+Nscz5RqN5G7rM8JDXv8Q@mail.gmail.com> (raw)
In-Reply-To: <1627029074-23449-1-git-send-email-skakit@codeaurora.org>
Quoting satya priya (2021-07-23 01:31:11)
> satya priya (3):
> dt-bindings: mfd: pm8008: Add gpio-ranges and spmi-gpio compatible
> dt-bindings: pinctrl: qcom-pmic-gpio: Convert qcom pmic gpio bindings
> to YAML
> dt-bindings: pinctrl: qcom-pmic-gpio: Remove the interrupts property
>
Which tree is this series going to be merged through? bindings, gpio?
next prev parent reply other threads:[~2021-07-26 23:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 8:31 [PATCH V7 0/3] Convert qcom pmic gpio bindings to YAML satya priya
2021-07-23 8:31 ` [PATCH V7 1/3] dt-bindings: mfd: pm8008: Add gpio-ranges and spmi-gpio compatible satya priya
2021-07-23 22:58 ` Rob Herring
2021-07-25 18:17 ` Bjorn Andersson
2021-07-27 22:19 ` Guru Das Srinagesh
2021-08-02 8:11 ` Lee Jones
2021-07-23 8:31 ` [PATCH V7 2/3] dt-bindings: pinctrl: qcom-pmic-gpio: Convert qcom pmic gpio bindings to YAML satya priya
2021-07-23 8:31 ` [PATCH V7 3/3] dt-bindings: pinctrl: qcom-pmic-gpio: Remove the interrupts property satya priya
2021-07-26 23:10 ` Stephen Boyd [this message]
2021-07-30 9:58 ` [PATCH V7 0/3] Convert qcom pmic gpio bindings to YAML Linus Walleij
2021-08-02 12:59 ` skakit
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='CAE-0n53bqJ8iBwBRwwf=-Fob5AObe+Nscz5RqN5G7rM8JDXv8Q@mail.gmail.com' \
--to=swboyd@chromium.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=gurus@codeaurora.org \
--cc=kgunda@codeaurora.org \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=skakit@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 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.