public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: torvalds@linux-foundation.org
Cc: akpm@linux-foundation.org, linux-ide@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [GIT]: IDE fixes
Date: Thu, 25 Jun 2009 03:03:43 -0700 (PDT)	[thread overview]
Message-ID: <20090625.030343.140417558.davem@davemloft.net> (raw)


1) Fix regressions wrt. unexpected IRQs during early device
   probe and startup.  From Bart.

2) Because the ID block bits were busted at the time of the
   call, until that was fixed the DMA info validity checker
   was always checking garbage.  Usually zeros.

   Now that it isn't checking garbage, it's triggering for
   all kinds of devices.  Those devices always functioned
   properly so the warning checks are just noise.

   So we simply remove them.  Fix from Bart.

3) cs5520's second port IRQ wasn't being setup properly.  With
   help from Bart and Alan Cox.

4) ide-cd had some warnings added when the CDROM advertises a
   strange block size.  But this check is overzealous, and since
   the code does correct the value it's only valuable to print
   this warning once instead of spamming your kernel log file
   every time your some daemon checks the CDROM for a present
   disc.

   From Frans Pop and your's truly.

5) Quantum fireball with APL.090 firmware needs ivb_list[] cable
   detection workaround.  From Bart.

6) Power management handling of requests isn't air tight.  Fix
   from Bart.

Please pull, thanks!

The following changes since commit 4e8a2372f9255a1464ef488ed925455f53fbdaa1:
  Mikael Pettersson (1):
        nvidiafb: fix boot-time printk string

are available in the git repository at:

  master.kernel.org:/pub/scm/linux/kernel/git/davem/ide-2.6.git master

Bartlomiej Zolnierkiewicz (4):
      ide: fix handling of unexpected IRQs vs request_irq()
      ide: relax DMA info validity checking
      ide: add QUANTUM FIREBALLct20 30 with firmware APL.090 to ivb_list[]
      ide: improve handling of Power Management requests

David S. Miller (2):
      ide-cd: Don't warn on bogus block size unless it actually matters.
      ide cs5520: Initialize second port's interrupt number.

Frans Pop (1):
      ide-cd: Improve "weird block size" error message

 drivers/ide/cs5520.c    |    1 +
 drivers/ide/ide-cd.c    |   10 +++++---
 drivers/ide/ide-dma.c   |   21 ------------------
 drivers/ide/ide-io.c    |   54 +++++++++++++++++++---------------------------
 drivers/ide/ide-iops.c  |    4 +--
 drivers/ide/ide-probe.c |   23 +++++++++++++++++--
 include/linux/ide.h     |    2 -
 7 files changed, 50 insertions(+), 65 deletions(-)

             reply	other threads:[~2009-06-25 10:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-25 10:03 David Miller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-06-30  2:54 [GIT]: IDE fixes David Miller
2009-06-22  9:42 David Miller
2009-06-22 17:40 ` Linus Torvalds
2009-06-22 21:20   ` Bartlomiej Zolnierkiewicz
2009-06-22 21:57   ` David Miller
2009-06-22 22:06     ` Bartlomiej Zolnierkiewicz
2009-06-22 22:03       ` David Miller

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=20090625.030343.140417558.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=akpm@linux-foundation.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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