From: Tom Rini <trini@konsulko.com>
To: Lokesh Vutla <lokeshvutla@ti.com>, Tero Kristo <kristo@kernel.org>
Cc: u-boot@lists.denx.de
Subject: Re: [GIT PULL v2] TI changes for v2021.10 next
Date: Sun, 13 Jun 2021 12:49:45 -0400 [thread overview]
Message-ID: <20210613164945.GZ9516@bill-the-cat> (raw)
In-Reply-To: <20210611161014.23043-1-lokeshvutla@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1262 bytes --]
On Fri, Jun 11, 2021 at 09:40:14PM +0530, Lokesh Vutla wrote:
> Hi Tom,
> Please find the PR for master branch targeted for v2021.10-next branch
> with checkpatch warnings fixed. Details about the PR are updated in the tag message.
>
> Gitlab CI report: https://source.denx.de/u-boot/custodians/u-boot-ti/-/pipelines/7817
>
> The following changes since commit e8f720ee1707b43a0e14ade87b40a1f84baeb2f3:
>
> Merge branch '2021-06-08-kconfig-migrations' into next (2021-06-09 08:19:13 -0400)
>
> are available in the Git repository at:
>
> https://source.denx.de/u-boot/custodians/u-boot-ti.git tags/ti-v2021.10-next-v2
>
> for you to fetch changes up to 5abb694d6016eaf497c3d9a3ec79382e217e7508:
>
> dma: ti: k3-udma: Add support for native configuration of chan/flow (2021-06-11 19:18:52 +0530)
>
I've applied this to u-boot/next now. But please follow up to fix:
w+(j7200_evm_a72 j721e_evm_a72 j721e_hs_evm_a72 j7200_evm_r5
j721e_evm_r5 j721e_hs_evm_r5)
arch/arm/dts/k3-j7200-common-proc-board.dtb: Warning (reg_format):
/bus@100000/bus@28380000/mcu-navss/ringacc@2b800000:reg: property has
invalid length (80 bytes) (#address-cells == 2, #size-cells == 1)
and all of the other dtc warnings. Thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2021-06-13 16:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 16:10 [GIT PULL v2] TI changes for v2021.10 next Lokesh Vutla
2021-06-13 16:49 ` Tom Rini [this message]
2021-06-14 8:05 ` Tero Kristo
2021-06-14 8:17 ` Vignesh Raghavendra
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=20210613164945.GZ9516@bill-the-cat \
--to=trini@konsulko.com \
--cc=kristo@kernel.org \
--cc=lokeshvutla@ti.com \
--cc=u-boot@lists.denx.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).