qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Harsh Prateek Bora <harshpb@linux.ibm.com>,
	BALATON Zoltan <balaton@eik.bme.hu>,
	Cornelia Huck <cohuck@redhat.com>,
	Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: Nicholas Piggin <npiggin@gmail.com>,
	qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Subject: Re: [PATCH] hw/ppc/sam460ex: Update u-boot-sam460ex
Date: Wed, 29 Oct 2025 07:52:55 +0100	[thread overview]
Message-ID: <46ac8536-58e9-407e-9ec5-e0e6c67fd80a@redhat.com> (raw)
In-Reply-To: <ee77b09f-7a12-4d52-b5f6-2d4b5b711448@linux.ibm.com>

On 29/10/2025 07.31, Harsh Prateek Bora wrote:
> + Thomas
> 
> Hi BALATON,
> 
> I am unable to fetch it with b4 am, and I do not see it appear on lore also, 
> not sure if its due to the binary size.
> 
> harshpb:patches$ b4 am 20251028151923.10DBB5972E5@zero.eik.bme.hu
> Looking up https://lore.kernel.org/ 
> r/20251028151923.10DBB5972E5%40zero.eik.bme.hu
> Grabbing thread from lore.kernel.org/ 
> all/20251028151923.10DBB5972E5%40zero.eik.bme.hu/t.mbox.gz
> Server returned an error: 404
> harshpb:patches$
> 
> I guess you may need to send a PULL SUBSYSTEM req like Thomas did for slof:
> https://lore.kernel.org/qemu-devel/20251027074404.25758-1-thuth@redhat.com/
> 
> Hi Thomas,
> Is it a known thing to deal with binary updates ?

  Hi,

honestly, I can't remember clearly why we introduced these subsystem pull 
requests in the past ... Maybe it was related to some problems with binary 
patches, but I think it was rather meant as a staged approach for the case 
where the maintainer of the firmware is not the main maintainer of the 
architecture subsystem, so that the main maintainer gets another chance of 
doing tests before the final pull request to the master branch.

Conny, Alexey, do you remember?

  Thomas



       reply	other threads:[~2025-10-29  6:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251028151923.10DBB5972E5@zero.eik.bme.hu>
     [not found] ` <ee77b09f-7a12-4d52-b5f6-2d4b5b711448@linux.ibm.com>
2025-10-29  6:52   ` Thomas Huth [this message]
2025-10-29  9:24     ` [PATCH] hw/ppc/sam460ex: Update u-boot-sam460ex Cornelia Huck
2025-10-29  9:58   ` BALATON Zoltan
2025-10-29 10:23     ` Harsh Prateek Bora
2025-10-29 10:39       ` BALATON Zoltan
2025-10-29 10:56         ` Harsh Prateek Bora
2025-10-29 13:18           ` BALATON Zoltan

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=46ac8536-58e9-407e-9ec5-e0e6c67fd80a@redhat.com \
    --to=thuth@redhat.com \
    --cc=aik@ozlabs.ru \
    --cc=balaton@eik.bme.hu \
    --cc=cohuck@redhat.com \
    --cc=harshpb@linux.ibm.com \
    --cc=npiggin@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.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 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).