From: Dan Williams <dan.j.williams@intel.com>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org,
jack_wang@usish.com
Subject: Re: [GIT PATCH v4 0/2] libsas: eh reworks (ata-eh vs discovery, races, ...)
Date: Mon, 16 Jan 2012 12:44:14 -0800 [thread overview]
Message-ID: <CAA9_cmcJ7vnc1xq_3s1UU+nEF+bHS+O+xc65m3Mim6bWs1uTDQ@mail.gmail.com> (raw)
In-Reply-To: <1326745447.2872.28.camel@dabdike>
On Mon, Jan 16, 2012 at 12:24 PM, James Bottomley
<James.Bottomley@hansenpartnership.com> wrote:
>> I managed to confuse things by posting only incremental series... the
>> full set is in git, and I can repost as needed.
>
> Well, no, when I asked you said the libsas series was pending rewrite.
> Specifically
>
> [PATCH v3 03/14] libsas: prevent domain rediscovery competing with ata
> error handling
>
> I think ... have you reposted that?
>
Well, only in incremental diff form (at the start of this thread).
Let me go ahead repost v4 and include the patches that got refreshed.
...and we can leave off the regression fixes from v5 till post -rc1 I assume.
--
Dan
next prev parent reply other threads:[~2012-01-16 20:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 7:38 [GIT PATCH v4 0/2] libsas: eh reworks (ata-eh vs discovery, races, ...) Dan Williams
2012-01-10 7:38 ` [PATCH v4 1/2] libsas: pre-clean commands that won the eh vs completion race Dan Williams
2012-01-10 7:38 ` [PATCH v4 2/2] libsas: feed the scsi_block_when_processing_errors() meter Dan Williams
2012-01-10 19:29 ` [GIT PATCH v4 0/2] libsas: eh reworks (ata-eh vs discovery, races, ...) James Bottomley
2012-01-10 20:18 ` Dan Williams
2012-01-16 8:40 ` James Bottomley
2012-01-16 17:00 ` Dan Williams
2012-01-16 20:24 ` James Bottomley
2012-01-16 20:44 ` Dan Williams [this message]
2012-01-13 0:57 ` Jack Wang
2012-01-13 1:21 ` Dan Williams
2012-01-13 1:37 ` Jack Wang
2012-01-13 1:51 ` Dan Williams
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=CAA9_cmcJ7vnc1xq_3s1UU+nEF+bHS+O+xc65m3Mim6bWs1uTDQ@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=jack_wang@usish.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.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 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.