From: Douglas Gilbert <dougg@torque.net>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org,
htejun@gmail.com, russb@emc.com
Subject: Re: [PATCH 0/3] libata: scsi error handling, encore
Date: Sat, 15 Oct 2005 12:30:59 +1000 [thread overview]
Message-ID: <435069E3.90306@torque.net> (raw)
In-Reply-To: <434919E4.1080601@pobox.com>
Jeff Garzik wrote:
> Douglas Gilbert wrote:
>
>> This is a series of patches that are equivalent to
>> one sent on 2005/09/19:
>> "[PATCH] libata: scsi error handling, lk 2.6.14-rc1"
>> http://marc.theaimsgroup.com/?l=linux-scsi&m=112711945709949&w=2
>>
>> The aim is to build more general sense buffers for SCSI
>> errors detected in the SCSI ATA translation layer in libata.
>> These patches are against Jeff's libata-dev git repository,
>> upstream branch.
>> Patch 1: adds ata_scsi_set_sense() extern declaration and
>> definition
>> Patch 2: switch error processing in libata-scsi.c to use
>> ata_scsi_set_sense()
>> Patch 3: remove static inline definitions in libata.h that
>> are no longer used after patch 2
>>
>> Signed-off-by: Douglas Gilbert <dougg@torque.net>
>
>
> First and foremost, applied all three patches. Thanks for your
> patience. 'upstream' branch will reflect your changes as soon as
> master.kernel.org propagates to the public mirrors.
Jeff,
Six days have passed and "git pull ..../libata-dev" still
does not reflect these changes. Am I doing something
wrong? Should I wait before submitting more changes?
Doug Gilbert
next prev parent reply other threads:[~2005-10-15 2:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-09 12:23 [PATCH 0/3] libata: scsi error handling, encore Douglas Gilbert
2005-10-09 13:23 ` Jeff Garzik
2005-10-09 17:30 ` Luben Tuikov
2005-10-09 17:43 ` Jeff Garzik
2005-10-15 2:30 ` Douglas Gilbert [this message]
2005-10-15 2:34 ` Jeff Garzik
2005-10-15 3:46 ` Douglas Gilbert
2005-10-15 3:54 ` Tejun Heo
2005-10-15 3:55 ` Tejun Heo
2005-10-18 21:06 ` Jeff Garzik
2005-10-19 3:47 ` Tejun Heo
2005-10-15 5:08 ` Albert Lee
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=435069E3.90306@torque.net \
--to=dougg@torque.net \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=russb@emc.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).