From: Jeff Garzik <jgarzik@pobox.com>
To: Mark Lord <mlord@pobox.com>
Cc: Linux IDE mailing list <linux-ide@vger.kernel.org>
Subject: Re: [PATCH 01/06] sata_mv: cache frequently read registers
Date: Wed, 25 Feb 2009 15:20:56 -0500 [thread overview]
Message-ID: <49A5A828.1090300@pobox.com> (raw)
In-Reply-To: <499A26B8.7070107@pobox.com>
Mark Lord wrote:
> Jeff Garzik wrote:
> ..
>> ACK patches 1-6
>>
>> however, they do not seem to apply to libata-dev.git#upstream, which
>> already has several sata_mv changes in it.
>>
>> Can you regenerate please? No need to copy the list on resend, unless
>> the patch content changes....
> ..
>
> Mmm.. strange. Here (attached) are the six patches again,
> along with what my git here gives for the upstream copy of sata_mv.c
> from *before* applying the patches.
Sorry for the delay... the attachments applied and worked just fine.
I eyeballed the first patch and it looked the same as your emailed first
patch, so I'm guessing there was an email bugaboo somewhere, rather than
a patch content problem.
Applied all 6 to #upstream.
Jeff
prev parent reply other threads:[~2009-02-25 20:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-13 5:03 [PATCH 01/06] sata_mv: cache frequently read registers Mark Lord
2009-02-13 5:05 ` [PATCH 02/06] sata_mv: enable ATAPI DMA for GEN_IIE chips Mark Lord
2009-02-13 5:05 ` [PATCH 03/06] sata_mv: stricter irq masking Mark Lord
2009-02-13 5:08 ` [PATCH 04/06] sata_mv: implement mv_sff_check_status Mark Lord
2009-02-13 5:08 ` [PATCH 05/06] sata_mv: export ata_pio_queue_task() Mark Lord
2009-02-13 5:09 ` [PATCH 06/06] sata_mv: implement mv_qc_issue_fis() for errata workaround Mark Lord
2009-02-17 0:19 ` [PATCH 01/06] sata_mv: cache frequently read registers Jeff Garzik
2009-02-25 17:52 ` Mark Lord
[not found] ` <499A26B8.7070107@pobox.com>
2009-02-25 20:20 ` Jeff Garzik [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=49A5A828.1090300@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=mlord@pobox.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).