mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Haverkamp <markh@osdl.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Russell King <rmk@arm.linux.org.uk>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>, Pat Mochel <mochel@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] pci bridge class code
Date: 02 Jun 2003 07:25:56 -0700	[thread overview]
Message-ID: <1054563956.20579.10.camel@markh1.pdx.osdl.net> (raw)
In-Reply-To: <1054557568.535.47.camel@gaston>

On Mon, 2003-06-02 at 05:39, Benjamin Herrenschmidt wrote:
> On Mon, 2003-06-02 at 14:32, Russell King wrote:
> 
> > That would not help the case when you have the "generic" bridge module
> > loaded and the specific bridge driver as a loadable module.
> 
> Well... we could store the match score of the driver, and if a newer
> driver comes with a better match, call a replace() callback in the
> current owner to ask if it allows "live" replacement... But that's
> far beyond my original idea though

That is something I was considering also. I'm not sure how big of a
change it would be yet.  I started looking at it a little bit on Friday.

Mark.

-- 
Mark Haverkamp <markh@osdl.org>


  reply	other threads:[~2003-06-02 14:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-29 20:17 Mark Haverkamp
2003-05-29 20:40 ` Russell King
2003-05-30  9:44   ` Alan Cox
2003-06-02 11:56     ` Benjamin Herrenschmidt
2003-06-02 12:32       ` Russell King
2003-06-02 12:39         ` Benjamin Herrenschmidt
2003-06-02 14:25           ` Mark Haverkamp [this message]
2003-05-30 23:13 ` Greg KH
2003-06-02 20:30   ` Mark Haverkamp
2003-06-02 20:35     ` Greg KH

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=1054563956.20579.10.camel@markh1.pdx.osdl.net \
    --to=markh@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@osdl.org \
    --cc=rmk@arm.linux.org.uk \
    /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®