qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: kwolf@redhat.com, pbonzini@redhat.com, qemu-devel@nongnu.org,
	stefanha@redhat.com, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH 00/15] AHCI test helper refactors
Date: Fri, 19 Sep 2014 11:28:59 -0400	[thread overview]
Message-ID: <541C4BBB.1060802@redhat.com> (raw)
In-Reply-To: <87k34znaot.fsf@blackfin.pond.sub.org>



On 09/19/2014 06:53 AM, Markus Armbruster wrote:
> John Snow <jsnow@redhat.com> writes:
>
>> The original version of the AHCI test base
>> which is now staged for being merged, processes
>> the ahci_identify test in a monolithic fashion.
>>
>> In authoring new tests, it became necessary and
>> obvious as to how the operation of this device
>> should be factored out to ease the writing of
>> new AHCI tests.
>>
>> This patch set issues the necessary refactorings
>> to support future test development for AHCI.
>>
>> This patch set DOES NOT account for any new fixes
>> and requires no fixes from my "AHCI fixes" RFC
>> in order to run successfully on 2014-09-18's
>> origin/master.
>>
>> This patch set does not alter the operation of the
>> existing test, or add new tests. It only offers
>> refactorings for future patch submissions which
>> depend on them, but are still under consideration.
> [...]
>>   tests/ahci-test.c | 860 ++++++++++++++++++++++++++++++++++++------------------
>>   1 file changed, 583 insertions(+), 277 deletions(-)
>
> Ignorant question: why should we commit the "monolithic" test only to
> refactor it extensively right away?
>

Newbie problems, basically.

I submitted the first AHCI test series 2014-07-07. The tests were staged 
last week. A lot happened on my downstream copy in that time, but I 
opted to keep the series "the same scope" from v1 through v4, because 
otherwise the series would have just kept growing ... I submitted v4

I do apologize at how absurd it is, on your end, to see an introduction 
followed immediately by a refactor. It seemed like the idea at the time 
was to get a basis that people agreed upon, then modify as needed.

Sorry for the confusion.

-- 
—js

  parent reply	other threads:[~2014-09-19 15:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-18 23:43 [Qemu-devel] [PATCH 00/15] AHCI test helper refactors John Snow
2014-09-18 23:43 ` [Qemu-devel] [PATCH 01/15] qtest/ahci: Add AHCIState structure John Snow
2014-09-18 23:43 ` [Qemu-devel] [PATCH 02/15] qtest/ahci: Add port_select helper John Snow
2014-09-18 23:43 ` [Qemu-devel] [PATCH 03/15] qtest/ahci: Add port_clear helper John Snow
2014-09-18 23:43 ` [Qemu-devel] [PATCH 04/15] qtest/ahci: Add command header helpers John Snow
2014-09-18 23:43 ` [Qemu-devel] [PATCH 05/15] qtest/ahci: Add build cmd table helper John Snow
2014-09-18 23:43 ` [Qemu-devel] [PATCH 06/15] qtest/ahci: Add link_cmd_slot helper John Snow
2014-09-18 23:43 ` [Qemu-devel] [PATCH 07/15] qtest/ahci: Add port_check_error helper John Snow
2014-09-18 23:43 ` [Qemu-devel] [PATCH 08/15] qtest/ahci: Add issue_command helper John Snow
2014-09-18 23:43 ` [Qemu-devel] [PATCH 09/15] qtest/ahci: Add port_check_interrupts helper John Snow
2014-09-18 23:43 ` [Qemu-devel] [PATCH 10/15] qtest/ahci: Add port_check_nonbusy helper John Snow
2014-09-18 23:43 ` [Qemu-devel] [PATCH 11/15] qtest/ahci: Add cmd response sanity check helpers John Snow
2014-09-18 23:43 ` [Qemu-devel] [PATCH 12/15] qtest/ahci: Enforce zero-leaks for guest mem usage John Snow
2014-09-18 23:43 ` [Qemu-devel] [PATCH 13/15] qtest/ahci: Add a macro bootup routine John Snow
2014-09-18 23:43 ` [Qemu-devel] [PATCH 14/15] qtest/ahci: Add human-readable command names John Snow
2014-09-18 23:43 ` [Qemu-devel] [PATCH 15/15] qtest/ahci: Don't use a magic constant for buffer size John Snow
2014-09-19 10:53 ` [Qemu-devel] [PATCH 00/15] AHCI test helper refactors Markus Armbruster
2014-09-19 12:57   ` Stefan Hajnoczi
2014-09-19 15:28   ` John Snow [this message]
2014-11-03 18:41 ` John Snow
2015-01-08 16:25 ` John Snow

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=541C4BBB.1060802@redhat.com \
    --to=jsnow@redhat.com \
    --cc=armbru@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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).