From: Etienne Basset <etienne.basset@numericable.fr>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kernel Testers List <kernel-testers@vger.kernel.org>,
Maciej Rutecki <maciej.rutecki@gmail.com>
Subject: Re: [Bug #15549] [2.6.34-rc1][libata] regression?
Date: Mon, 22 Mar 2010 20:50:16 +0100 [thread overview]
Message-ID: <4BA7C9F8.30000@numericable.fr> (raw)
In-Reply-To: <fa.ZWYjYwS2FWNa/1ZvJa5P5hXf5J0@ifi.uio.no>
Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a summary report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.33. Please verify if it still should be listed and let the tracking team
> know (either way).
>
>
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15549
> Subject : [2.6.34-rc1][libata] regression?
> Submitter : Etienne Basset <etienne.basset@numericable.fr>
> Date : 2010-03-09 21:47 (13 days old)
> Message-ID : <4B96C202.6050606@numericable.fr>
> References : http://marc.info/?l=linux-kernel&m=126817180811846&w=2
>
>
hello,
this can be closed, it is a duplicate of #15537; the patch attached to 15537 helps but is not yet upstream
thanks,
Etienne
next parent reply other threads:[~2010-03-22 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.0ATnC9jnJLEG9H3v5nxRBlETRRs@ifi.uio.no>
[not found] ` <fa.ZWYjYwS2FWNa/1ZvJa5P5hXf5J0@ifi.uio.no>
2010-03-22 19:50 ` Etienne Basset [this message]
[not found] ` <4BA7C9F8.30000-Bf/eaXMDFuuXqB7oj33eUg@public.gmane.org>
2010-03-22 21:22 ` [Bug #15549] [2.6.34-rc1][libata] regression? Rafael J. Wysocki
2010-03-22 21:22 ` Rafael J. Wysocki
2010-03-21 19:58 2.6.34-rc2: Reported regressions from 2.6.33 Rafael J. Wysocki
2010-03-21 20:13 ` [Bug #15549] [2.6.34-rc1][libata] regression? Rafael J. Wysocki
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=4BA7C9F8.30000@numericable.fr \
--to=etienne.basset@numericable.fr \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.rutecki@gmail.com \
--cc=rjw@sisk.pl \
/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.