qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: "Igor V. Kovalenko" <igor.v.kovalenko@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] cmd646: amend bmdma issue fix
Date: Sun, 2 May 2010 00:05:27 +0300	[thread overview]
Message-ID: <o2vf43fc5581005011405hcf8effadmbd73b083a7bac4cd@mail.gmail.com> (raw)
In-Reply-To: <20100422215238.19357.13159.stgit@skyserv>

Thanks, applied.

On 4/23/10, Igor V. Kovalenko <igor.v.kovalenko@gmail.com> wrote:
> Hi!
>
>  The following series are not picked from mailing list, so this is a resend.
>
>  Short history is that original fix for cmd646 bmdma issue was done by
>  reverting pci_dev removal from driver. That was a quick workaround
>  and later Juan was kind enough to improve driver code.
>
>  Patches on the list:
>   - http://lists.gnu.org/archive/html/qemu-devel/2009-12/msg01421.html
>   - http://lists.gnu.org/archive/html/qemu-devel/2009-12/msg01439.html
>
>  ---
>
>  Igor V. Kovalenko (2):
>       cmd646: pass pci_dev as it needs it
>       cmd646: fix abort due to changed opaque pointer for ioport read
>
>
>   hw/ide/cmd646.c   |   66 +++++++++++++++++++++++++++++++++++++++--------------
>   hw/ide/internal.h |    1 -
>   hw/ide/piix.c     |    1 -
>   3 files changed, 48 insertions(+), 20 deletions(-)
>
>  --
>  Kind regards,
>
> Igor V. Kovalenko
>
>
>

      parent reply	other threads:[~2010-05-01 21:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-22 21:54 [Qemu-devel] [PATCH 0/2] cmd646: amend bmdma issue fix Igor V. Kovalenko
2010-04-22 21:54 ` [Qemu-devel] [PATCH 1/2] cmd646: pass pci_dev as it needs it Igor V. Kovalenko
2010-04-22 21:54 ` [Qemu-devel] [PATCH 2/2] cmd646: fix abort due to changed opaque pointer for ioport read Igor V. Kovalenko
2010-05-01 21:05 ` Blue Swirl [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=o2vf43fc5581005011405hcf8effadmbd73b083a7bac4cd@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=igor.v.kovalenko@gmail.com \
    --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).