All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Sommrey <jo@sommrey.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [SATA] libata-dev queue updated
Date: Thu, 3 Mar 2005 20:32:29 +0100	[thread overview]
Message-ID: <20050303193229.GA10265@sommrey.de> (raw)
In-Reply-To: <422641AF.8070309@pobox.com>

On Wed, Mar 02, 2005 at 05:43:59PM -0500, Jeff Garzik wrote:
> Joerg Sommrey wrote:
> >Jeff Garzik wrote:
> >>Patch:
> >>http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.11-rc5-bk4-libata-dev1.patch.bz2
> >
> >
> >Still not usable here.  The same errors as before when backing up:
> 
> Please try 2.6.11 without any patches.
Plain 2.6.11 doesn't work either.  All of 2.6.10-ac11, 2.6.11-rc5,
2.6.11-rc5 + 2.6.11-rc5-bk4-libata-dev1.patch and 2.6.11 fail with the
same symptoms. 

Reverting to stable 2.6.10-ac8 :-)

-jo

-- 
-rw-r--r--  1 jo users 63 2005-03-03 20:23 /home/jo/.signature

  reply	other threads:[~2005-03-03 19:43 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3Ds62-5AS-3@gated-at.bofh.it>
2005-03-02 20:34 ` [SATA] libata-dev queue updated Joerg Sommrey
2005-03-02 22:43   ` Jeff Garzik
2005-03-03 19:32     ` Joerg Sommrey [this message]
2005-03-04  4:09       ` Jeff Garzik
2005-03-04  6:37         ` Joerg Sommrey
2005-03-04  7:10           ` Jeff Garzik
2005-03-04 17:49             ` Joerg Sommrey
2005-03-04 18:07               ` Jeff Garzik
2005-03-04 20:33                 ` Joerg Sommrey
2005-03-04 20:43                   ` Jeff Garzik
2005-03-04 22:06                     ` Joerg Sommrey
2005-03-04 22:32                       ` Joerg Sommrey
2005-06-07  7:00 Bene Martin
2005-06-07  7:00 ` Bene Martin
  -- strict thread matches above, loose matches on Subject: below --
2005-06-04  6:08 Jeff Garzik
2005-06-04 15:17 ` Greg Stark
2005-06-04 17:48   ` Jeff Garzik
2005-06-04 18:50     ` Adrian Bunk
2005-06-04 19:05       ` Jeff Garzik
2005-06-04 19:15         ` Greg Stark
2005-06-04 19:19           ` Jeff Garzik
2005-06-05  2:25             ` Greg Stark
2005-06-05  2:30               ` Jeff Garzik
2005-06-05  5:30                 ` Greg Stark
2005-06-22 16:15                 ` Mark Lord
2005-06-22 20:23                   ` Jeff Garzik
2005-06-23  3:39                     ` Mark Lord
2005-06-05  2:40               ` Drew Winstel
2005-06-05  2:58               ` Jim Crilly
2005-06-06 16:01   ` Mark Lord
2005-06-07  1:57     ` Greg Stark
2005-06-07 11:20       ` Brad Campbell
2005-06-08  8:33         ` Mark Lord
2005-06-07 13:15           ` Brad Campbell
2005-06-08  8:37       ` Mark Lord
2005-06-07 13:51         ` Greg Stark
2005-06-08 10:30           ` Mark Lord
2005-06-08  8:51       ` Mark Lord
2005-06-07 13:09         ` Domenico Andreoli
2005-06-07 17:53         ` Jeff Garzik
2005-03-10  5:40 Jeff Garzik
2005-03-29  9:12 ` kern.petr
2005-03-08 11:20 Jeff Garzik
2005-03-02  2:40 Jeff Garzik
2005-02-19  8:40 Jeff Garzik
2005-02-19 16:58 ` Andre Tomt
2005-02-19 17:09   ` Jeff Garzik
2005-02-13 20:33 Jeff Garzik
2004-10-30 16:15 Jeff Garzik
2004-10-27  6:52 Jeff Garzik
2004-10-27  6:53 ` Jeff Garzik
2004-10-27 22:53 ` Rob van Nieuwkerk
2004-10-27 23:03   ` Jeff Garzik
2004-10-18 23:52 Jeff Garzik
2004-10-16  0:44 Jeff Garzik
2004-10-15  8:04 Jeff Garzik
2004-10-15 17:15 ` Jeff Garzik

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=20050303193229.GA10265@sommrey.de \
    --to=jo@sommrey.de \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@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.