linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Maxime Ripard <mripard@kernel.org>
Cc: SoC Team <soc@kernel.org>, ARM-SoC Maintainers <arm@kernel.org>,
	Chen-Yu Tsai <wens@csie.org>,
	Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] Allwinner Device Tree Changes for 5.6
Date: Sun, 12 Jan 2020 11:52:47 -0800	[thread overview]
Message-ID: <CAOesGMgWc4XBDSXnRsQ_Ba4oB0uvh5mgDq7Nj6P7FM6BhVdcyg@mail.gmail.com> (raw)
In-Reply-To: <20200112134933.sq7njjxdm5gxtmek@gilmour.lan>

On Sun, Jan 12, 2020 at 5:49 AM Maxime Ripard <mripard@kernel.org> wrote:
>
> Hi,
>
> On Sat, Jan 11, 2020 at 02:59:38PM -0800, Olof Johansson wrote:
> > On Fri, Jan 10, 2020 at 06:14:51PM +0100, Maxime Ripard wrote:
> > > Please pull the following changes for the next release.
> > >
> > > Thanks!
> > > Maxime
> > >
> > > The following changes since commit e42617b825f8073569da76dc4510bfa019b1c35a:
> > >
> > >   Linux 5.5-rc1 (2019-12-08 14:57:55 -0800)
> > >
> > > are available in the Git repository at:
> > >
> > >   https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git refs/tags/sunxi-dt-for-5.6
> > >
> > > for you to fetch changes up to 6163ce8467052cdfe42581036bc71fe4aac09eab:
> > >
> > >   arm64: dts: allwinner: a64: enable DVFS (2020-01-09 17:31:39 +0100)
> > >
> > > ----------------------------------------------------------------
> > > This is our usual set of DT patches for the Allwinner SoCs.
> > >
> > > It's fairly big this time, but the highlights are:
> > >   - Enable cpufreq and CPU thermal throttling on the A64
> > >   - CSI0 support on the R40
> > >   - CSI1 support on the A10 and A20
> > >   - SPI support on the R40
> > >   - PMU support on the H3, H5, H6 and R40
> > >   - MIPI-DSI support on the A64
> > >   - PWM support on the H6
> > >   - Thermal sensor on the A64, A83t, H3, H5, H6 and R40
> > >   - More DT schemas fixes and conversions
> > >   - New boards: LibreComputer ALL-H5-CC H5, LibreComputer ALL-H3-IT H5,
> > >                 Pine64 H64 Model B, Neutis N5H3
> >
> > This doesn't build for arm64 defconfig. What happened at your end
> > that made this slip through your testing? :(
>
> The patch in question is using a define that was merged into a
> separate branch, and I only tested the result of the merge between the
> two branches... Sorry.

It happens. Might be worth running each pull request through a quick
test at your end to avoid it in the future. Ideally we'll set up
automation on patchwork for it at some point as well, so we can catch
it pre-merge.

> > I've had to rebase arm/dt to drop this branch. Please send a new tested/fixed
> > version.
>
> Ok, I will, thanks!

Sounds good.

-Olof

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2020-01-12 19:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-10 17:14 [GIT PULL] Allwinner Device Tree Changes for 5.6 Maxime Ripard
2020-01-11 22:59 ` Olof Johansson
2020-01-12 13:49   ` Maxime Ripard
2020-01-12 19:52     ` Olof Johansson [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=CAOesGMgWc4XBDSXnRsQ_Ba4oB0uvh5mgDq7Nj6P7FM6BhVdcyg@mail.gmail.com \
    --to=olof@lixom.net \
    --cc=arm@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mripard@kernel.org \
    --cc=soc@kernel.org \
    --cc=wens@csie.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).