All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: "Ian McDonald" <ian.mcdonald@jandi.co.nz>
Cc: gregkh@suse.de,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Tejun Heo" <htejun@gmail.com>, Jeff Garzik <jeff@garzik.org>
Subject: Re: [BUG/WARN] Error initialising drivers in PCI
Date: Mon, 19 Feb 2007 12:47:03 +0100	[thread overview]
Message-ID: <200702191247.03274.bzolnier@gmail.com> (raw)
In-Reply-To: <5640c7e00702182000p26f1ca8n15c1edcd8b3134a1@mail.gmail.com>


On Monday 19 February 2007 05:00, Ian McDonald wrote:
> On 2/19/07, Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> wrote:
> > Ian, you have an PATA controller so there is no need to use ata_piix.
> > Just disabling ata_piix should workaround the issue.
> >
> OK. I have done this and the message goes away in boot logs. As you
> say I don't need the old drivers anymore.

No, I said that you don't need the new drivers anymore as the warning
is caused by libata using resource hacks. 8)

Anyway both drivers (old and new) work fine, just mixing them have issues.

> If you want me to test any fixes so both can coexist without throwing
> a warning then just drop me a line.

Tejun, this needs to be fixed unless Jeff pushes resources hack
removal patch(es) before 2.6.21 (then it will fix by itself).

Thanks,
Bart

  reply	other threads:[~2007-02-19 11:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-18 19:53 [BUG/WARN] Error initialising drivers in PCI Ian McDonald
2007-02-18 20:58 ` Bartlomiej Zolnierkiewicz
2007-02-19  4:00   ` Ian McDonald
2007-02-19 11:47     ` Bartlomiej Zolnierkiewicz [this message]
2007-02-20  8:28       ` [PATCH] pci: allow multiple calls to pcim_pin_device() Tejun Heo
2007-02-20 21:45         ` Ian McDonald

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=200702191247.03274.bzolnier@gmail.com \
    --to=bzolnier@gmail.com \
    --cc=gregkh@suse.de \
    --cc=htejun@gmail.com \
    --cc=ian.mcdonald@jandi.co.nz \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.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 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.