From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Niklas Cassel <Niklas.Cassel@wdc.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Kevin Wolf <kwolf@redhat.com>
Cc: John Snow <jsnow@redhat.com>,
"qemu-block@nongnu.org" <qemu-block@nongnu.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Damien Le Moal <dlemoal@kernel.org>
Subject: Re: [PATCH v3 0/8] misc AHCI cleanups
Date: Tue, 25 Jul 2023 14:58:55 +0200 [thread overview]
Message-ID: <b58779ed-cecb-824b-019e-bc34e6b2258a@linaro.org> (raw)
In-Reply-To: <ZLe/VG5d6TEdp/MT@x1-carbon>
Hi Niklas, John, Paolo, Kevin,
On 19/7/23 12:47, Niklas Cassel wrote:
>> Niklas Cassel (8):
>> hw/ide/ahci: remove stray backslash
>> hw/ide/core: set ERR_STAT in unsupported command completion
>> hw/ide/ahci: write D2H FIS when processing NCQ command
>> hw/ide/ahci: simplify and document PxCI handling
>> hw/ide/ahci: PxSACT and PxCI is cleared when PxCMD.ST is cleared
>> hw/ide/ahci: PxCI should not get cleared when ERR_STAT is set
>> hw/ide/ahci: fix ahci_write_fis_sdb()
>> hw/ide/ahci: fix broken SError handling
>>
>> hw/ide/ahci.c | 112 +++++++++++++++++++++++++++-----------
>> hw/ide/core.c | 2 +-
>> tests/qtest/libqos/ahci.c | 106 +++++++++++++++++++++++++++---------
>> tests/qtest/libqos/ahci.h | 8 +--
>> 4 files changed, 164 insertions(+), 64 deletions(-)
>>
>> --
>> 2.40.1
>>
>>
>
> Hello Philippe,
>
> Considering that you picked up my patch,
> "hw/ide/ahci: remove stray backslash" (patch 1/8 in this series),
> and since John seems to have gone silent for 40+ days,
> could you please consider taking this series through your misc tree?
(First patch was a cleanup)
Niklas, I don't feel confident enough :/
John, Paolo, Kevin, do you Ack?
Regards,
Phil.
next prev parent reply other threads:[~2023-07-25 12:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 14:08 [PATCH v3 0/8] misc AHCI cleanups Niklas Cassel
2023-06-09 14:08 ` [PATCH v3 1/8] hw/ide/ahci: remove stray backslash Niklas Cassel
2023-06-09 14:08 ` [PATCH v3 2/8] hw/ide/core: set ERR_STAT in unsupported command completion Niklas Cassel
2023-07-19 11:43 ` Philippe Mathieu-Daudé
2023-06-09 14:08 ` [PATCH v3 3/8] hw/ide/ahci: write D2H FIS when processing NCQ command Niklas Cassel
2023-06-09 14:08 ` [PATCH v3 4/8] hw/ide/ahci: simplify and document PxCI handling Niklas Cassel
2023-06-09 14:08 ` [PATCH v3 5/8] hw/ide/ahci: PxSACT and PxCI is cleared when PxCMD.ST is cleared Niklas Cassel
2023-07-19 11:50 ` Philippe Mathieu-Daudé
2023-06-09 14:08 ` [PATCH v3 6/8] hw/ide/ahci: PxCI should not get cleared when ERR_STAT is set Niklas Cassel
2023-06-09 14:08 ` [PATCH v3 7/8] hw/ide/ahci: fix ahci_write_fis_sdb() Niklas Cassel
2023-07-19 11:53 ` Philippe Mathieu-Daudé
2023-06-09 14:08 ` [PATCH v3 8/8] hw/ide/ahci: fix broken SError handling Niklas Cassel
2023-07-19 11:59 ` Philippe Mathieu-Daudé
2023-07-19 12:06 ` Michael Tokarev
2023-07-19 12:11 ` Philippe Mathieu-Daudé
2023-07-19 10:47 ` [PATCH v3 0/8] misc AHCI cleanups Niklas Cassel
2023-07-25 12:58 ` Philippe Mathieu-Daudé [this message]
2023-07-25 19:00 ` John Snow
2023-08-07 10:32 ` Niklas Cassel
2023-08-07 17:37 ` John Snow
2023-08-31 8:32 ` Philippe Mathieu-Daudé
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=b58779ed-cecb-824b-019e-bc34e6b2258a@linaro.org \
--to=philmd@linaro.org \
--cc=Niklas.Cassel@wdc.com \
--cc=dlemoal@kernel.org \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@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).