All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Dinh Nguyen <dinguyen@kernel.org>, soc@kernel.org
Subject: Re: [GIT PULL 1/2] SoCFPGA DTS updates for v7.4
Date: Wed, 21 Oct 2026 20:26:05 +0200	[thread overview]
Message-ID: <202610211826058f634946@mail.local> (raw)
In-Reply-To: <f6262d7d-d5da-4be3-b37a-81ba3e35bba5@app.fastmail.com>

On 21/10/2026 18:46:39+0200, Arnd Bergmann wrote:
> On Mon, Oct 19, 2026, at 15:21, Dinh Nguyen wrote:
> > On 10/14/26 02:06, Arnd Bergmann wrote:
> >> On Wed, Oct 14, 2026, at 01:33, Dinh Nguyen wrote:
> >>>
> >>> I see that the bot has pull in the 2/2 of PR, but something may have
> >>> gone wrong with the PR 1/2?
> >>>
> >>> I may have done something wrong? Can you please take a look?
> >> 
> >> We tend to pull in similar branches from different submitters together,
> >> I only got through the defconfig, drivers and arm32 branches yesterday,
> >> the DT branches should get there in the next few days. It's a bit late
> >> because of lpc, but unless something shows up it should be there in
> >> the next two days.
> >
> > Sorry to bother you guys again, but I still don't see the commits in 
> > this PR in any of the soc branches. Please let me know if there's any I 
> > need to do.
> 
> Hi Dinh,
> 
> Sorry for missing this: Alexandre pointed out that when he looked
> at the branch it was not part of linux-next and did not pull it,
> and I assumed that he had notified you about it when I did the
> final merges for 7.4.
> 
> I see that you have a for-next branch with a different set of commit
> IDs but overlapping contents. Can you explain what is going on?
> I normall expect that whatever you send for inclusion in the soc
> tree has seen some time in linux-next using the exact git commits.
> 
> I fear that at this point it is a little late to take either
> version of the branch, but it would be nice if you could see
> if there are important changes (not new features) that you can rebase
> and send for the first set of fixes that can still make it into -rc1.
> 

My mistake, I forgot to notify, I wanted to sort out whether the new
dtbs_check warnings I had where due to the renaming or had another
reason.

After removing some false positives, the issues were:

cbce4a0dacb6: arm64: dts: intel: agilex5: add USB3.1 controller node
      + /soc@0/bus@11000000/usb@0: failed to match any schema with compatible: ['altr,agilex5-dwc3']
        from arch/arm64/boot/dts/altera/socfpga_agilex5.dtsi:534 (dtsi)

The issue here is that GKH never took the related dt-bindings, I
believe because Krzysztof had comments on it.

29f11fb83ad5: arm64: dts: agilex5: add support for debug daughter card
      + /soc@0/spi@10da4000/eeprom@0: failed to match any schema with compatible: ['microchip,25aa128', 'atmel,at25']
        from arch/arm64/boot/dts/altera/socfpga_agilex5_socdk_debug.dts:101 (dts)


It seems that there is a different version of the branch in linux-next.

-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2026-10-21 18:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-08 16:47 [GIT PULL 1/2] SoCFPGA DTS updates for v7.4 Dinh Nguyen
2026-10-13 16:10 ` patchwork-bot+linux-soc
2026-10-13 23:33   ` Dinh Nguyen
2026-10-14  7:06     ` Arnd Bergmann
2026-10-19 13:21       ` Dinh Nguyen
2026-10-21 16:46         ` Arnd Bergmann
2026-10-21 18:26           ` Alexandre Belloni [this message]
2026-10-21 20:33             ` Dinh Nguyen
2026-10-21 22:11               ` Arnd Bergmann

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=202610211826058f634946@mail.local \
    --to=alexandre.belloni@bootlin.com \
    --cc=arnd@arndb.de \
    --cc=dinguyen@kernel.org \
    --cc=soc@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.