From: Andy Gross <andy.gross@linaro.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: arm-soc <arm@kernel.org>, Kevin Hilman <khilman@baylibre.com>,
Olof Johansson <olof@lixom.net>,
linux-arm-msm@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Doug Anderson <dianders@chromium.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>
Subject: Re: [GIT PULL] Qualcomm Device Tree updates for 4.20
Date: Fri, 5 Oct 2018 09:28:31 -0500 [thread overview]
Message-ID: <20181005142831.GB15665@hector.nxp.com> (raw)
In-Reply-To: <CAK8P3a3SVftnc83sxe1NCsLbu23Buc+SHOpn9JUQJCZ=MXDuJw@mail.gmail.com>
On Tue, Oct 02, 2018 at 11:36:11AM +0200, Arnd Bergmann wrote:
> On Sun, Sep 30, 2018 at 8:38 PM Andy Gross <andy.gross@linaro.org> wrote:
> >
> > The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
> >
> > Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)
> >
> > are available in the git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/agross/linux.git tags/qcom-dts-for-4.20
> >
> > for you to fetch changes up to ca02f96b95ca1a50344e7e2a7bb43fbb825aa3a2:
> >
> > ARM: dts: qcom: Update coresight bindings for hardware ports (2018-09-30 13:14:05 -0500)
> >
> > ----------------------------------------------------------------
> > Qualcomm Device Tree Changes for v4.20
> >
> > * Fix IRQ constants usage on MSM8974
> > * Add led, gpio-button, sdcc, and pcie nodes for IPQ8064
> > * Move/cleanup common nodes for IPQ8064
> > * Add i2c sensor nodes for MSM8974 Hammerhead
> > * Fixes for SAW, kpss, opp, pci range, and space/tab on IPQ4019
> > * Update coresight bindings
>
> Some of the ipq4019 changes look like important fixes, should
> they be applied for linux-4.19 and possibly backported to stable?
> If so, please submit them again for the fixes branch.
>
> I also get this one warning (both with and without your patches):
>
> arch/arm/boot/dts/qcom-apq8064-arrow-sd-600eval.dtb: Warning
> (graph_endpoint): /soc/mdp@5100000/ports/port@3/endpoint: graph
> connection to node '/soc/hdmi-tx@4a00000/ports/port@0/endpoint' is not
> bidirectional
We may very well drop the sd600. It was not distributed in any large numbers,
was only used for development. I am in the process of determining whether or
not to send the patch removing this entirely.
Andy
next prev parent reply other threads:[~2018-10-05 14:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-30 18:37 [GIT PULL] Qualcomm ARM64 Defconfig updates for 4.20 Andy Gross
2018-09-30 18:37 ` [GIT PULL] Qualcomm ARM64 DT " Andy Gross
2018-10-02 9:30 ` Arnd Bergmann
2018-10-05 14:29 ` Andy Gross
2018-10-25 5:25 ` Amit Kucheria
2018-10-25 16:08 ` Andy Gross
2018-10-28 17:54 ` Amit Kucheria
2018-11-07 6:15 ` Amit Kucheria
2018-09-30 18:38 ` [GIT PULL] Qualcomm Defconfig " Andy Gross
2018-10-01 15:59 ` Arnd Bergmann
2018-09-30 18:38 ` [GIT PULL] Qualcomm Driver " Andy Gross
2018-10-02 8:14 ` Arnd Bergmann
2018-09-30 18:38 ` [GIT PULL] Qualcomm Device Tree " Andy Gross
2018-10-02 9:36 ` Arnd Bergmann
2018-10-05 14:28 ` Andy Gross [this message]
2018-10-05 14:31 ` Arnd Bergmann
2018-11-29 10:10 ` Clément Péron
2018-10-01 16:00 ` [GIT PULL] Qualcomm ARM64 Defconfig " Arnd Bergmann
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=20181005142831.GB15665@hector.nxp.com \
--to=andy.gross@linaro.org \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@linaro.org \
--cc=dianders@chromium.org \
--cc=khilman@baylibre.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
/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).