From: "Arnd Bergmann" <arnd@kernel.org>
To: "Jeremy J. Peper" <jeremy@jeremypeper.com>, linux-kernel@vger.kernel.org
Cc: "Andrew Lunn" <andrew@lunn.ch>,
"Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com>,
"Gregory Clement" <gregory.clement@bootlin.com>,
"Russell King" <linux@armlinux.org.uk>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/4] adjust init logic for ts-wxl to reflect single core dev
Date: Fri, 17 Mar 2023 16:52:04 +0100 [thread overview]
Message-ID: <ed327f8d-ac9f-454c-a005-0edb400be165@app.fastmail.com> (raw)
In-Reply-To: <20230317154411.3727514-1-jeremy@jeremypeper.com>
On Fri, Mar 17, 2023, at 16:43, Jeremy J. Peper wrote:
> Original code was largely copy-pasted from the reference board code,
> adjust pcie initialiazation to reflect the TS-WXL using the single-core
> variant of this SoC.
> Correct pcie_port_size to be a power of 2 as required.
>
> Signed-off-by: Jeremy J. Peper <jeremy@jeremypeper.com>
All four patches look good to me in this version,
Reviewed-by: Arnd Bergmann <arnd@arndb.de>
Andrew/Sebastian/Gregory, please let me know if you have any comments
on this, and if you want to pick it up in the mvebu tree or I should
just apply them directly in the soc tree to save you the work.
If I apply them directly, I'd probably take patches 1, 2 and 4 as
bugfixes for 6.3, but leave patch 3 for the 6.4 merge window, unless
you have a different preference.
Arnd
prev parent reply other threads:[~2023-03-17 15:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 15:43 Jeremy J. Peper
2023-03-17 15:43 ` [PATCH 2/4] set the correct driver for the i2c RTC Jeremy J. Peper
2023-03-17 15:43 ` [PATCH 3/4] add code to enable XOR and CRYPTO engines on mv78xx0 Jeremy J. Peper
2023-03-17 15:43 ` [PATCH 4/4] fix entries for gpios, buttons and usb ports Jeremy J. Peper
2023-03-17 15:52 ` Arnd Bergmann [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=ed327f8d-ac9f-454c-a005-0edb400be165@app.fastmail.com \
--to=arnd@kernel.org \
--cc=andrew@lunn.ch \
--cc=gregory.clement@bootlin.com \
--cc=jeremy@jeremypeper.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=sebastian.hesselbarth@gmail.com \
/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
all inboxes | Powered by JetHome®