u-boot.lists.denx.de archive mirror
 help / color / mirror / Atom feed
From: Vignesh Raghavendra <vigneshr@ti.com>
To: Tero Kristo <kristo@kernel.org>, Tom Rini <trini@konsulko.com>,
	Lokesh Vutla <lokeshvutla@ti.com>
Cc: <u-boot@lists.denx.de>
Subject: Re: [GIT PULL v2] TI changes for v2021.10 next
Date: Mon, 14 Jun 2021 13:47:54 +0530	[thread overview]
Message-ID: <8dc29f72-237d-99fc-0346-56765ec6d577@ti.com> (raw)
In-Reply-To: <eb37bcc8-a339-09da-d4ee-b349ea0c96ba@kernel.org>



On 6/14/21 1:35 PM, Tero Kristo wrote:
> On 13/06/2021 19:49, Tom Rini wrote:
>> 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!
>>
> 
> Thanks a lot Tom!
> 
> I think those DTC warnings are coming out of the DMA support series from
> Vignesh. Vignesh, any comments?
> 

I had provided a diff to squash at [1]. Looks like that was
not picked up. Will send a follow up patch.

[1] https://lore.kernel.org/u-boot/c8a8bad1-cd13-344e-5701-02748bb005b3@ti.com/

      reply	other threads:[~2021-06-14  8:18 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
2021-06-14  8:05   ` Tero Kristo
2021-06-14  8:17     ` Vignesh Raghavendra [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=8dc29f72-237d-99fc-0346-56765ec6d577@ti.com \
    --to=vigneshr@ti.com \
    --cc=kristo@kernel.org \
    --cc=lokeshvutla@ti.com \
    --cc=trini@konsulko.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 NNTP newsgroup(s).