All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Lev Kujawski <lkujaw@member.fsf.org>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
	qemu-block@nongnu.org, Laurent Vivier <lvivier@redhat.com>,
	Thomas Huth <thuth@redhat.com>, John Snow <jsnow@redhat.com>
Subject: Re: [PATCH v2 1/7] piix_ide_reset: Use pci_set_* functions instead of direct access
Date: Fri, 30 Sep 2022 17:17:18 +0200	[thread overview]
Message-ID: <YzcIfokJyBmjji+D@redhat.com> (raw)
In-Reply-To: <20220707031140.158958-1-lkujaw@member.fsf.org>

Am 07.07.2022 um 05:11 hat Lev Kujawski geschrieben:
> Eliminate the remaining TODOs in hw/ide/piix.c by:
> * Using pci_set_{size} functions to write the PIIX PCI configuration
>   space instead of manipulating it directly as an array; and
> * Documenting the default register values by reference to the
>   controlling specification.
> 
> Signed-off-by: Lev Kujawski <lkujaw@member.fsf.org>

Thanks, dropped patches 5 and 6 because I see that you have posted a
newer version of them, and applied the rest to the block branch.

Kevin



      parent reply	other threads:[~2022-09-30 15:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-07  3:11 [PATCH v2 1/7] piix_ide_reset: Use pci_set_* functions instead of direct access Lev Kujawski
2022-07-07  3:11 ` [PATCH v2 2/7] tests/qtest/ide-test.c: Create disk image for use as a secondary Lev Kujawski
2022-07-07  3:11 ` [PATCH v2 3/7] hw/ide/core: Clear LBA and drive bits for EXECUTE DEVICE DIAGNOSTIC Lev Kujawski
2022-07-07  3:11 ` [PATCH v2 4/7] tests/qtest/ide-test: Verify that DIAGNOSTIC clears DEV to zero Lev Kujawski
2022-07-07  3:11 ` [PATCH v2 5/7] qpci_device_enable: Allow for command bits hardwired to 0 Lev Kujawski
2022-07-07  3:11 ` [PATCH v2 6/7] hw/ide/piix: Ignore writes of hardwired PCI command register bits Lev Kujawski
2022-07-07  3:11 ` [PATCH v2 7/7] hw/ide/core.c: Implement ATA INITIALIZE_DEVICE_PARAMETERS command Lev Kujawski
2022-09-30 15:17 ` Kevin Wolf [this message]

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=YzcIfokJyBmjji+D@redhat.com \
    --to=kwolf@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=lkujaw@member.fsf.org \
    --cc=lvivier@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@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 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.