From: "Konstantin Ryabitsev" <konstantin.ryabitsev@linux.dev>
To: "Manorit Chawdhry" <m-chawdhry@ti.com>, "Nishanth Menon" <nm@ti.com>
Cc: "Tom Rini" <trini@konsulko.com>,
u-boot@lists.denx.de, "Vignesh Raghavendra" <vigneshr@ti.com>,
"Neha Malcom Francis" <n-francis@ti.com>,
"Udit Kumar" <u-kumar1@ti.com>, "Reid Tonking" <reidt@ti.com>,
"Apurva Nandan" <a-nandan@ti.com>, "Andrew Davis" <afd@ti.com>,
"Nikhil M Jain" <n-jain1@ti.com>
Subject: Re: [PATCH] J721S2 DTS Sync from v6.6-rc1 to u-boot
Date: Tue, 19 Sep 2023 17:26:36 +0000 [thread overview]
Message-ID: <3cf2e853b134779ae0f3809321cc6289ceda1802@linux.dev> (raw)
In-Reply-To: <20230919112053.g2dwnssl7s7hqjo5@ula0497581>
September 19, 2023 at 7:20 AM, "Manorit Chawdhry" <m-chawdhry@ti.com> wrote:
> Am not sure either.. I had been using b4 for all the patches and I still
> see that my next revision queued by b4 also has the same problem. Not
> exactly sure what went wrong with b4 but would be careful next time.
> Thanks for pointing it out.
I'm curious how this happened as well.
Can you please send me the output of:
b4 prep --version
b4 prep --show-info (while in the branch that caused this problem)
-K
next prev parent reply other threads:[~2023-09-19 21:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 8:39 [PATCH] J721S2 DTS Sync from v6.6-rc1 to u-boot Manorit Chawdhry
2023-09-19 8:39 ` [PATCH] configs: j721s2_evm_r5_defconfig: Increase malloc pool size in DRAM Manorit Chawdhry
2023-09-19 8:39 ` [PATCH] Revert "arm: dts: k3-j7*: ddr: Update to 0.10 version of DDR config tool" Manorit Chawdhry
2023-09-19 8:39 ` [PATCH] arm: mach-k3: j721s2: Add mcu_timer0 id to the dev list Manorit Chawdhry
2023-09-19 8:39 ` [PATCH] k3-j721s2: Sync from Linux tag v6.6-rc1 Manorit Chawdhry
2023-09-19 8:39 ` [PATCH] k3-am68: " Manorit Chawdhry
2023-09-19 8:39 ` [PATCH] docs: board: ti: Add j721s2_evm documentation Manorit Chawdhry
2023-09-19 8:39 ` [PATCH] board: ti: j721s2: MAINTAINERS: Update the MAINTAINERS File Manorit Chawdhry
2023-09-19 11:13 ` [PATCH] J721S2 DTS Sync from v6.6-rc1 to u-boot Nishanth Menon
2023-09-19 11:20 ` Manorit Chawdhry
2023-09-19 12:05 ` Nishanth Menon
2023-09-19 17:26 ` Konstantin Ryabitsev [this message]
2023-09-20 4:39 ` Manorit Chawdhry
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=3cf2e853b134779ae0f3809321cc6289ceda1802@linux.dev \
--to=konstantin.ryabitsev@linux.dev \
--cc=a-nandan@ti.com \
--cc=afd@ti.com \
--cc=m-chawdhry@ti.com \
--cc=n-francis@ti.com \
--cc=n-jain1@ti.com \
--cc=nm@ti.com \
--cc=reidt@ti.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=u-kumar1@ti.com \
--cc=vigneshr@ti.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