From: Gerd Hoffmann <kraxel@redhat.com>
To: Sam Eiderman <sameid@google.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
seabios@seabios.org, Laszlo Ersek <lersek@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [SeaBIOS] Re: [PATCH] ahci: zero-initialize port struct
Date: Fri, 15 Nov 2019 07:54:22 +0100 [thread overview]
Message-ID: <20191115065422.rqu74yt2r3asnk35@sirius.home.kraxel.org> (raw)
In-Reply-To: <CAFr6bUmUxN4k4AhNOZZxwXUY3uEZZHAwuno4bCvedKFJuuRp8w@mail.gmail.com>
On Thu, Nov 14, 2019 at 11:08:59AM +0200, Sam Eiderman wrote:
> Do you want a single commit with the changes?
That is the idea, unless it is too messy. I don't have v4 any more,
looks like I've deleted v4 instead of v3 while cleaning up my mail
folders, so I can't easily check. Do you have v3 and v4 as git
branches somewhere?
> I am afraid it will be slightly unreadable when looking at file histories.
> The only commit that didn't change was:
> [SeaBIOS] [PATCH v4 2/5] boot: Reorder functions in boot.c
Hmm, looks like there have been more changes than I remember.
Maybe it's better to revert and re-apply the changed patches
then.
cheers,
Gerd
next prev parent reply other threads:[~2019-11-15 6:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 9:18 [PATCH] ahci: zero-initialize port struct Gerd Hoffmann
2019-11-13 9:35 ` Laszlo Ersek
2019-11-13 14:00 ` [SeaBIOS] " Gerd Hoffmann
2019-11-13 15:03 ` Sam Eiderman
2019-11-13 15:18 ` Sam Eiderman
2019-11-13 15:46 ` Sam Eiderman
2019-11-13 16:12 ` Philippe Mathieu-Daudé
2019-11-13 16:35 ` Sam Eiderman
2019-11-13 16:46 ` Sam Eiderman
2019-11-14 7:20 ` Gerd Hoffmann
2019-11-14 9:08 ` Sam Eiderman
2019-11-15 6:54 ` Gerd Hoffmann [this message]
2019-11-15 11:35 ` Gerd Hoffmann
2019-11-15 11:50 ` Sam Eiderman
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=20191115065422.rqu74yt2r3asnk35@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=lersek@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sameid@google.com \
--cc=seabios@seabios.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).