From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jeff Garzik <jeff@garzik.org>
Cc: Meelis Roos <mroos@linux.ee>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Linux IDE mailing list <linux-ide@vger.kernel.org>
Subject: Re: pata_cmd64x broken in 2.6.33-rc1 on sparc64
Date: Sun, 20 Dec 2009 00:37:01 +0000 [thread overview]
Message-ID: <20091220003701.7c5a0257@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <4B2D54AC.3080509@garzik.org>
> > mice: PS/2 mouse device common for all mice
> > ------------[ cut here ]------------
> > WARNING: at drivers/ata/pata_cmd64x.c:268 cmd64x_bmdma_stop+0x3c/0x60()
Which version of the cmd64x patch got applied ?
> Does backing out the following commit fix things?
>
> commit d43744390e460dce6626fb8de2c02a24ff650005
> Author: Alan Cox <alan@linux.intel.com>
> Date: Mon Nov 30 13:22:54 2009 +0000
>
> pata_cmd64x: implement serialization as per notes
>
> Although quite unlikely, commit f0353813afe784330622596ff141e7525ccd99de
> may also change things. Try backing that out, if backing out the first
> commit (d43744...) fails to improve behavior.
I'll take a look at this after new year but it looks like the old version
ended up in the libata tree without the additional fixes, if so its
pretty trivial to sort out (see Bartlomiej response to the original and
the follow up thread plus fixes)
next prev parent reply other threads:[~2009-12-20 0:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-19 22:23 Meelis Roos
2009-12-19 22:26 ` David Miller
2009-12-19 22:33 ` Jeff Garzik
2009-12-20 0:37 ` Alan Cox [this message]
2009-12-20 1:38 ` Mikael Pettersson
2009-12-20 0:41 ` Alan Cox
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=20091220003701.7c5a0257@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
/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
all inboxes | Powered by JetHome®