public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mathis Ahrens <Mathis.Ahrens@gmx.de>
To: Russ Dill <russ.dill@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Reporting result of pci=assign-busses to lkml
Date: Wed, 15 Aug 2007 16:23:04 +0200	[thread overview]
Message-ID: <46C30C48.70905@gmx.de> (raw)
In-Reply-To: <f9d2a5e10708102011o7d61086fs9e2b35abca9b39a3@mail.gmail.com>


Hi Russ,

in case you are still wondering about this...

There is a good explanation of the original reasoning here:
    http://lists.opensuse.org/opensuse-bugs/2007-02/msg00149.html

And there are plans to remove the message here
    http://www.uwsg.iu.edu/hypermail/linux/kernel/0707.3/2879.html

I am still seeing the warning in 2.6.23-rc3, but it makes no difference
if I specify pci=assign-busses ... everything seems fine either way.

Cheers,
Mathis

      reply	other threads:[~2007-08-15 14:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-11  3:11 Reporting result of pci=assign-busses to lkml Russ Dill
2007-08-15 14:23 ` Mathis Ahrens [this message]

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=46C30C48.70905@gmx.de \
    --to=mathis.ahrens@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=russ.dill@gmail.com \
    /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