[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20210127172914.1ffac2a2@slackpad.fritz.box>
Date: Wed, 27 Jan 2021 17:29:14 +0000
From: Andre Przywara <andre.przywara@....com>
To: Mark Brown <broonie@...nel.org>
Cc: Maxime Ripard <mripard@...nel.org>, Chen-Yu Tsai <wens@...e.org>,
Clément Péron <peron.clem@...il.com>,
Ulf Hansson <ulf.hansson@...aro.org>,
Linus Walleij <linus.walleij@...aro.org>,
Yangtao Li <tiny.windzz@...il.com>,
Shuosheng Huang <huangshuosheng@...winnertech.com>,
Jernej Skrabec <jernej.skrabec@...l.net>,
Icenowy Zheng <icenowy@...c.io>, linux-sunxi@...glegroups.com,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
Samuel Holland <samuel@...lland.org>
Subject: Re: (subset) [PATCH v4 00/21] arm64: sunxi: Initial Allwinner H616
SoC support
On Wed, 27 Jan 2021 17:15:30 +0000
Mark Brown <broonie@...nel.org> wrote:
> On Mon, 25 Jan 2021 15:17:50 +0000, Andre Przywara wrote:
> > an update from the v3 last week, to add support for the Allwinner H616
> > SoC. Still based on the (updated) sunxi/for-next branch.
> > I am omitting the MMC and pinctrl patches now, as they have been taken
> > by Ulf and LinusW already into their trees.
> >
> > I addressed the comments from the list, though not sure if the HOSC clock
> > coming from the RTC is really a good idea (didn't change it).
> >
> > [...]
>
> Applied to
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
>
> Thanks!
>
> [13/21] dt-bindings: spi: sunxi: Add H616 compatible string
> commit: 6589daf8bb98c75ad1065edad87c099ffb9f5d87
Thanks for that. I just sent a v5, just before seeing your email, so
this one still has this patch, but without any changes. So please
ignore [PATCH v5 13/21].
Cheers,
Andre
> All being well this means that it will be integrated into the linux-next
> tree (usually sometime in the next 24 hours) and sent to Linus during
> the next merge window (or sooner if it is a bug fix), however if
> problems are discovered then the patch may be dropped or reverted.
>
> You may get further e-mails resulting from automated or manual testing
> and review of the tree, please engage with people reporting problems and
> send followup patches addressing any issues that are reported if needed.
>
> If any updates are required or you are submitting further changes they
> should be sent as incremental updates against current git, existing
> patches will not be replaced.
>
> Please add any relevant lists and maintainers to the CCs when replying
> to this mail.
>
> Thanks,
> Mark
Powered by blists - more mailing lists