From: James Bottomley <James.Bottomley@SteelEye.com>
To: brking@linux.vnet.ibm.com
Cc: Jeff Garzik <jeff@garzik.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-ide@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git patches] libata reset sequence update
Date: Tue, 08 May 2007 10:43:29 -0500 [thread overview]
Message-ID: <1178639009.3737.23.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <46409865.9010204@linux.vnet.ibm.com>
On Tue, 2007-05-08 at 10:33 -0500, Brian King wrote:
> Jeff Garzik wrote:
> > This has been testing in -mm for a while, but I wanted to send it
> > separated from the main libata update, since it has a chance of
> > breakage.
> >
> > Most notably, a cumulative timeout (deadline) helps the code from diving
> > into overly-long reset sequences.
> >
> > Please pull from 'reset-seq' branch of
> > master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/libata-dev.git reset-seq
>
> James,
>
> FYI - this means you'll probably want to revert this patch:
>
> http://git.kernel.org/gitweb.cgi?p=linux/kernel/git/jejb/scsi-misc-2.6.git;a=commitdiff;h=a6506b8e111c9bf9e430e32725b96c0
Jeff,
I'm not happy about this ... I specifically put that reversion in
because you and Tejun told me the the reset change "is scheduled to be
merged but not too soon."
Since you knew I'd taken action on the basis of that advice, could you
at least cc me on the pull request that voids it?
I'll just pull it out of the scsi-misc tree.
James
prev parent reply other threads:[~2007-05-08 15:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 6:38 [git patches] libata reset sequence update Jeff Garzik
2007-05-08 15:33 ` Brian King
2007-05-08 15:43 ` James Bottomley [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=1178639009.3737.23.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@steeleye.com \
--cc=akpm@linux-foundation.org \
--cc=brking@linux.vnet.ibm.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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