mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: tcamuso@redhat.com
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
	"Schoeller, Patrick (Linux - Houston,
	TX)" <Patrick.Schoeller@hp.com>
Subject: Re: [PATCH] PCI: Correct last two HP entries in the bfsort whitelist
Date: Fri, 16 May 2008 10:29:55 -0700	[thread overview]
Message-ID: <200805161029.55649.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <482CB7D7.30008@redhat.com>

On Thursday, May 15, 2008 3:23 pm Tony Camuso wrote:
> Alan Cox wrote:
> > This is going to make everyone with those boxes who upgrades suddenely
> > get their devices re-ordered and renamed when the probe order changes.
> > That seems extremely inappropriate.
> >
> > Alan
>
> HP maintains that more of our customers, especially new customers,
> will be adversely affected by NOT implementing this patch for the
> following reasons.
>
> 1. HP issued a Customer Advisory for existing customers to use "pci=bfsort"
>     in the boot command for these systems. Customers using pci=bfsort in
>     their boot scripts will be unaffected by this patch.
>
> 2. Customers using only the two embedded NI devices will be unaffected.
>
> 3. Because of the use of labels for disk devices, they are unaffected.
>
> 4. New customers who must add pci=bfsort to their boot scripts have
>     expressed dissatisfaction.
>
> The only time this patch would induce any confusion for an existing
> customer is upon the convergence of the following situations.
>
> 1. The user has not followed the instructions in the release notes
>     for the DL360 and DL380,
>
>     AND
>
> 2. The user has added NI cards to the option slots,
>
>     AND
>
> 3. The user upgrades his kernel.

Ok, I'll put it in linux-next for now then.  It would be good to hear some 
feedback from users about it though...

Thanks,
Jesse

  reply	other threads:[~2008-05-16 17:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-15 18:40 Tony Camuso
2008-05-15 21:02 ` Alan Cox
2008-05-15 22:23   ` Tony Camuso
2008-05-16 17:29     ` Jesse Barnes [this message]
2008-05-16 19:04       ` Tony Camuso
2008-05-16 19:52       ` Tony Camuso
2008-05-20 17:53         ` Jesse Barnes

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=200805161029.55649.jbarnes@virtuousgeek.org \
    --to=jbarnes@virtuousgeek.org \
    --cc=Patrick.Schoeller@hp.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=tcamuso@redhat.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

all inboxes | Powered by JetHome®