From: "Cédric Le Goater" <clg@kaod.org>
To: "Richard Henderson" <richard.henderson@linaro.org>,
"Alexey Kardashevskiy" <aik@ozlabs.ru>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PULL SUBSYSTEM qemu-pseries] pseries: Update SLOF firmware image
Date: Wed, 17 Nov 2021 09:49:47 +0100 [thread overview]
Message-ID: <5d500a70-7240-d70b-eb3e-d06c8266e014@kaod.org> (raw)
In-Reply-To: <fe6d8599-49d6-779d-cfe9-7f5a7a48cd60@linaro.org>
On 11/17/21 09:39, Richard Henderson wrote:
> On 11/16/21 11:48 PM, Alexey Kardashevskiy wrote:
>> Yup. I am doing SLOF updates this way for ages after diifs became quite huge to make mailman barfing on the size, and the "subsystem" in the subj was the way to reduce the noise Peter had to respond to :)
>>
>> btw should I be signing those? I am not now.
>
> You could if you and Cedric want to do so (is it really Alexey sending the sub pr and not an impostor with access to the same github account?), but it will not leave a permanent record in the mainline history, because the merge object with the signature will be removed by any rebase.
Yes. I just noticed that the merge commit is lost :
2021-11-09 15:50 +0100 Christophe Lombard o [ppc-7.0] {origin/ppc-7.0} pci-host: Allow extended config space access for PowerNV PHB4 model
2021-11-16 17:39 +0100 Cédric Le Goater M─┐ Merge tag 'qemu-slof-20211112' of github.com:aik/qemu into ppc-7.0
2021-11-13 14:47 +1100 Alexey Kardashevskiy │ o pseries: Update SLOF firmware image
2021-11-12 12:28 +0100 Richard Henderson M─│─┐ Merge tag 'pull-ppc-20211112' of https://github.com/legoater/qemu into staging
2021-11-10 17:25 -0300 Daniel Henrique Barboza │ o─┘ {origin/ppc-for-upstream} {origin/ppc-next} <pull-ppc-20211112> ppc/mmu_helper.c: do not truncate 'ea
...
After rebase :
2021-11-09 15:50 +0100 Christophe Lombard o [ppc-7.0] pci-host: Allow extended config space access for PowerNV PHB4 model
2021-11-13 14:47 +1100 Alexey Kardashevskiy o pseries: Update SLOF firmware image
2021-11-16 21:07 +0100 Richard Henderson o Update version for v6.2.0-rc1 release
2021-11-16 18:55 +0100 Richard Henderson M─┐ Merge tag 'pull-nbd-2021-11-16' of https://repo.or.cz/qemu/ericb into staging
...
Alexey's commit appears in the list with only his SoB and we loose :
Merge tag 'qemu-slof-20211112' of github.com:aik/qemu into ppc-7.0
* tag 'qemu-slof-20211112' of github.com:aik/qemu:
pseries: Update SLOF firmware image
Signed-off-by: Cédric Le Goater <clg@kaod.org>
which I find interesting to identify where the SLOF blob is coming from.
Thanks,
C.
next prev parent reply other threads:[~2021-11-17 8:50 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-14 0:51 [PULL SUBSYSTEM qemu-pseries] pseries: Update SLOF firmware image Alexey Kardashevskiy
2021-11-16 16:46 ` Cédric Le Goater
2021-11-16 17:12 ` Philippe Mathieu-Daudé
2021-11-16 17:28 ` Richard Henderson
2021-11-16 17:30 ` Cédric Le Goater
2021-11-16 17:57 ` Philippe Mathieu-Daudé
2021-11-16 17:59 ` Cédric Le Goater
2021-11-16 22:48 ` Alexey Kardashevskiy
2021-11-17 8:39 ` Richard Henderson
2021-11-17 8:49 ` Cédric Le Goater [this message]
2021-11-17 11:43 ` Alexey Kardashevskiy
2021-11-17 12:01 ` Philippe Mathieu-Daudé
2021-11-18 14:42 ` Cédric Le Goater
-- strict thread matches above, loose matches on Subject: below --
2023-11-21 8:28 Alexey Kardashevskiy
2023-09-18 10:09 Alexey Kardashevskiy
2022-07-19 7:59 Alexey Kardashevskiy
2022-07-19 8:00 ` Alexey Kardashevskiy
2022-07-20 16:08 ` Daniel Henrique Barboza
2022-07-21 8:14 ` Alexey Kardashevskiy
2022-07-21 8:48 ` Peter Maydell
2022-07-21 9:03 ` Alexey Kardashevskiy
2022-07-22 0:35 ` Stefan Hajnoczi
2022-07-21 18:40 ` Stefan Hajnoczi
2022-07-21 18:51 ` Peter Maydell
2022-07-21 22:30 ` Stefan Hajnoczi
2022-01-10 5:04 Alexey Kardashevskiy
2022-01-10 6:50 ` Cédric Le Goater
2022-01-12 11:38 ` Cédric Le Goater
2022-07-19 4:55 ` Alexey Kardashevskiy
2021-07-11 14:10 Alexey Kardashevskiy
2021-02-19 4:13 Alexey Kardashevskiy
2021-02-22 6:07 ` David Gibson
2020-07-17 3:27 Alexey Kardashevskiy
2020-07-17 5:47 ` David Gibson
2020-05-13 2:43 Alexey Kardashevskiy
2020-06-02 11:39 ` Alexey Kardashevskiy
2020-03-27 3:02 Alexey Kardashevskiy
2020-03-16 23:33 Alexey Kardashevskiy
2020-03-17 1:11 ` David Gibson
2020-03-12 4:10 Alexey Kardashevskiy
2020-02-21 3:52 Alexey Kardashevskiy
2020-02-21 3:56 ` Alexey Kardashevskiy
2020-02-17 2:12 Alexey Kardashevskiy
2020-02-17 2:31 ` David Gibson
2020-02-17 9:26 ` Philippe Mathieu-Daudé
2020-02-17 10:24 ` Philippe Mathieu-Daudé
2020-02-17 22:46 ` David Gibson
2020-02-18 5:48 ` Philippe Mathieu-Daudé
2020-02-18 23:09 ` David Gibson
2020-02-21 4:09 ` Alexey Kardashevskiy
2020-02-21 5:43 ` David Gibson
2020-02-18 0:32 ` Alexey Kardashevskiy
2020-02-17 9:48 ` Cédric Le Goater
2020-02-18 0:30 ` Alexey Kardashevskiy
2020-02-18 7:12 ` Cédric Le Goater
2020-02-18 9:05 ` Alexey Kardashevskiy
2020-02-18 9:10 ` Alexey Kardashevskiy
2020-02-18 9:40 ` Cédric Le Goater
2020-02-18 12:48 ` Cédric Le Goater
2020-02-18 12:59 ` Cédric Le Goater
2020-02-18 23:10 ` David Gibson
2020-02-19 1:20 ` Alexey Kardashevskiy
2020-02-19 6:44 ` Alexey Kardashevskiy
2020-02-19 7:18 ` Cédric Le Goater
2020-02-20 1:50 ` Alexey Kardashevskiy
2020-02-20 7:31 ` Cédric Le Goater
2019-12-17 0:35 Alexey Kardashevskiy
2019-12-09 1:13 Alexey Kardashevskiy
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=5d500a70-7240-d70b-eb3e-d06c8266e014@kaod.org \
--to=clg@kaod.org \
--cc=aik@ozlabs.ru \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=richard.henderson@linaro.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.