LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [git patches] IDE updates part #4
Date: Tue, 5 Feb 2008 11:09:24 -0800 (PST)	[thread overview]
Message-ID: <alpine.LFD.1.00.0802051059330.3110@woody.linux-foundation.org> (raw)
In-Reply-To: <200802022035.02326.bzolnier@gmail.com>



On Sat, 2 Feb 2008, Bartlomiej Zolnierkiewicz wrote:
> 
> * next part of IDE probing code re-organization saga
>   (that would be me)

This seems to cause very irritating and bogus messages for me:

	Probing IDE interface ide0...
	Probing IDE interface ide1...
	ide2: I/O resource 0x0-0x7 not free.
	ide2: ports already in use, skipping probe
	ide3: I/O resource 0x0-0x7 not free.
	ide3: ports already in use, skipping probe
	ide4: I/O resource 0x0-0x7 not free.
	ide4: ports already in use, skipping probe
	ide5: I/O resource 0x0-0x7 not free.
	ide5: ports already in use, skipping probe
	ide6: I/O resource 0x0-0x7 not free.
	ide6: ports already in use, skipping probe
	ide7: I/O resource 0x0-0x7 not free.
	ide7: ports already in use, skipping probe
	ide8: I/O resource 0x0-0x7 not free.
	ide8: ports already in use, skipping probe
	ide9: I/O resource 0x0-0x7 not free.
	ide9: ports already in use, skipping probe

and that's just totally bogus. It shouldn't even request that region, 
since it's not been allocated!

So that "ide_device_add_all()" is missing some checks. Should it check the 
probe[] array like ideprobe_init() used to, or what?

		Linus

  reply	other threads:[~2008-02-05 19:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-02 19:35 Bartlomiej Zolnierkiewicz
2008-02-05 19:09 ` Linus Torvalds [this message]
2008-02-06  0:48   ` Bartlomiej Zolnierkiewicz
2008-04-27 14:26 [git patches] IDE updates part 4 Bartlomiej Zolnierkiewicz

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=alpine.LFD.1.00.0802051059330.3110@woody.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=bzolnier@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: [git patches] IDE updates part #4' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).