From: Mikael Pettersson <mikpe@it.uu.se>
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>,
IDE <linux-ide@vger.kernel.org>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
Mikael Pettersson <mikpe@it.uu.se>, Tejun Heo <tj@kernel.org>
Subject: Re: [Bug #13378] kernel/async.c broke pata_legacy.c
Date: Fri, 5 Jun 2009 14:41:18 +0200 [thread overview]
Message-ID: <18985.4718.192222.884806@pilspetsen.it.uu.se> (raw)
In-Reply-To: <LEcEO2518_I.A.8UD.tIbIKB@chimera>
Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.29. Please verify if it still should be listed and let me know
> (either way).
>
>
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=3D13378
> Subject : kernel/async.c broke pata_legacy.c
> Submitter : Mikael Pettersson <mikpe@it.uu.se>
> Date : 2009-05-24 16:13 (7 days old)
> References : http://marc.info/?l=3Dlinux-kernel&m=3D124318186507210&w=3D4
> Handled-By : James Bottomley <James.Bottomley@hansenpartnership.com>
> Patch : http://patchwork.kernel.org/patch/25699/
paga_legacy remains broken in 2.6.30-rc8, and I still have to
apply the above-mentioned patch to make the affected machine boot.
/Mikael
next prev parent reply other threads:[~2009-06-05 13:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4to6E2myxvG.A.muC.aIbIKB@chimera>
2009-05-30 19:37 ` [Bug #13378] kernel/async.c broke pata_legacy.c Rafael J. Wysocki
2009-06-05 12:41 ` Mikael Pettersson [this message]
2009-06-06 14:23 ` James Bottomley
[not found] ` <1244298195.14676.6.camel-0iu6Cu4xQGLYCGPCin2YbQ@public.gmane.org>
2009-06-06 22:34 ` 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=18985.4718.192222.884806@pilspetsen.it.uu.se \
--to=mikpe@it.uu.se \
--cc=James.Bottomley@hansenpartnership.com \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=tj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox