public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: "Thomas Lindroth" <thomas.lindroth@gmail.com>
Cc: "Alan Cox" <alan@lxorguk.ukuu.org.uk>,
	"Bartlomiej Zolnierkiewicz" <bzolnier@gmail.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	LKML <linux-kernel@vger.kernel.org>,
	"Linus Torvalds" <torvalds@linux-foundation.org>
Subject: Re: 2.6.24-rc2: Reported regressions from 2.6.23 (updated)
Date: Tue, 13 Nov 2007 11:52:28 -0800	[thread overview]
Message-ID: <20071113115228.b722ac51.akpm@linux-foundation.org> (raw)
In-Reply-To: <3d08dbff0711130534k702f66ebj1f8e91d107eff2a1@mail.gmail.com>

On Tue, 13 Nov 2007 14:34:19 +0100 "Thomas Lindroth" <thomas.lindroth@gmail.com> wrote:

> >
> > On Sun, 11 Nov 2007 22:46:43 +0000 Alan Cox <alan@lxorguk.ukuu.org.uk>
> > wrote:
> >
> > > > [PATCH] pata_amd/pata_via: de-couple programming of PIO/MWDMA and UDMA
> > timings
> > > >
> > > > * Don't program UDMA timings when programming PIO or MWDMA modes.
> > > >
> > > >   This has also a nice side-effect of fixing regression added by
> > commit
> > > >   681c80b5d96076f447e8101ac4325c82d8dce508 ("libata: correct handling
> > of
> > > >   SRST reset sequences") (->set_piomode method for PIO0 is called
> > before
> > > >   ->cable_detect method which checks UDMA timings to get the cable
> > type).
> > >
> > > I'm not sure this helps as if the ACPI _GTF method is looking at the
> > > flags and stuff but it has to be worth a try.
> > >
> > >
> > > Works for me as a 2.6.24 band aid
> >
> > I'm looking at that "Untested, please don't merge until it is confirmed to
> > fix the problem." comment..
> >
> > Thomas, can you please give it a try, let us know?
> >
> > Thanks
> >
> 
> I can confirm that the patch "pata_amd/pata_via: de-couple programming of
> PIO/MWDMA and UDMA timings" does fix my issue "pata_amd fails to detect
> 80-pin wire".
> 

Great, thanks for testing it.

I moved that patch to the "to send to maintainers as a 2.6.24 fix" queue. 
I should get all that material sent out hopefully tomorrow, if I can manage
to get 2.6.24-rc2-mm1 to limp out the door.

  parent reply	other threads:[~2007-11-13 19:58 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-11 19:58 2.6.24-rc2: Reported regressions from 2.6.23 (updated) Rafael J. Wysocki
2007-11-11 20:09 ` Alan Cox
2007-11-11 20:34   ` Rafael J. Wysocki
2007-11-11 22:22   ` Bartlomiej Zolnierkiewicz
2007-11-11 22:46     ` Alan Cox
2007-11-13  1:11       ` Andrew Morton
2007-11-13 14:09         ` Thomas Lindroth
     [not found]         ` <3d08dbff0711130534k702f66ebj1f8e91d107eff2a1@mail.gmail.com>
2007-11-13 19:52           ` Andrew Morton [this message]
2007-11-11 20:30 ` Ingo Molnar
2007-11-11 20:33 ` Francois Romieu
2007-11-14 11:20 ` [bug] SLOB crash, 2.6.24-rc2 Ingo Molnar
2007-11-14 17:36   ` Matt Mackall
2007-11-14 18:39     ` Matt Mackall
2007-11-14 19:05       ` Ingo Molnar
2007-11-14 19:42         ` Matt Mackall
2007-11-14 22:39         ` David Miller
2007-11-14 22:53           ` Matt Mackall
2007-11-14 23:10             ` David Miller
2007-11-14 23:37               ` Matt Mackall
2007-11-14 23:41                 ` David Miller
2007-11-15  0:09                   ` Matt Mackall
2007-11-15 10:43                   ` Ingo Molnar
2007-11-15 10:51                     ` David Miller
2007-11-15 11:03                       ` Ingo Molnar
2007-11-15 11:05                         ` David Miller
2007-11-15 10:57                     ` Nick Piggin
2007-11-15 11:28                       ` Ingo Molnar
2007-11-15 11:32                         ` [patch] slob: fix memory corruption Ingo Molnar
2007-11-15 12:48                           ` Ingo Molnar
2007-11-15 20:25                             ` Nick Piggin
2007-11-15 16:00                           ` Matt Mackall
2007-11-15 11:39                         ` [bug] SLOB crash, 2.6.24-rc2 Nick Piggin
2007-11-15 12:18                         ` Dave Haywood

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=20071113115228.b722ac51.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bzolnier@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=thomas.lindroth@gmail.com \
    --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