All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Joachim Fenkes <FENKES@de.ibm.com>
Cc: Thomas Q Klein <tklein@de.ibm.com>,
	Paul Mackerras <pmac@au1.ibm.com>,
	Jan-Bernd Themann <themann@de.ibm.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linuxppc-dev@ozlabs.org, Christoph Raisch <raisch@de.ibm.com>,
	Paul Mackerras <paulus@samba.org>,
	Stefan Roscher <stefan.roscher@de.ibm.com>
Subject: Re: [PATCH 2.6.23] ibmebus: Prevent bus_id collisions
Date: Fri, 31 Aug 2007 19:08:04 +0200	[thread overview]
Message-ID: <200708311908.05255.arnd@arndb.de> (raw)
In-Reply-To: <OFBB1BA4B6.29175A76-ONC1257348.004DBCB3-C1257348.0050161C@de.ibm.com>

On Friday 31 August 2007, Joachim Fenkes wrote:
> > The whole logic of dynamically adding and removing device is rather 
> bogus,
> > and it prevents autoloading of device drivers. of_platform_make_bus_id
> > is the function that is responsible for creating unique names over 
> there.
> 
> The plaintiff makes a valid point. How about a staging approach: We put 
> the patch as it is now into 2.6.23 so the problem is fixed, and I'll post 
> a "nice" version with autoloading support and a generic of_make_bus_id 
> function for 2.6.24. Agree?

Ok, sounds fair. Can you make sure that the resulting bus_id is the same
for the final version then?

	Arnd <><

WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Joachim Fenkes <FENKES@de.ibm.com>
Cc: Christoph Raisch <raisch@de.ibm.com>,
	Jan-Bernd Themann <themann@de.ibm.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
	Paul Mackerras <pmac@au1.ibm.com>,
	Stefan Roscher <stefan.roscher@de.ibm.com>,
	Thomas Q Klein <tklein@de.ibm.com>
Subject: Re: [PATCH 2.6.23] ibmebus: Prevent bus_id collisions
Date: Fri, 31 Aug 2007 19:08:04 +0200	[thread overview]
Message-ID: <200708311908.05255.arnd@arndb.de> (raw)
In-Reply-To: <OFBB1BA4B6.29175A76-ONC1257348.004DBCB3-C1257348.0050161C@de.ibm.com>

On Friday 31 August 2007, Joachim Fenkes wrote:
> > The whole logic of dynamically adding and removing device is rather 
> bogus,
> > and it prevents autoloading of device drivers. of_platform_make_bus_id
> > is the function that is responsible for creating unique names over 
> there.
> 
> The plaintiff makes a valid point. How about a staging approach: We put 
> the patch as it is now into 2.6.23 so the problem is fixed, and I'll post 
> a "nice" version with autoloading support and a generic of_make_bus_id 
> function for 2.6.24. Agree?

Ok, sounds fair. Can you make sure that the resulting bus_id is the same
for the final version then?

	Arnd <><

  reply	other threads:[~2007-08-31 17:10 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-29 16:15 [PATCH 2.6.23] ibmebus: Prevent bus_id collisions Joachim Fenkes
2007-08-29 16:15 ` Joachim Fenkes
2007-08-29 18:12 ` Nathan Lynch
2007-08-29 18:12   ` Nathan Lynch
2007-08-29 18:33 ` jschopp
2007-08-29 18:33   ` jschopp
2007-08-30 14:00   ` Joachim Fenkes
2007-08-30 14:00     ` Joachim Fenkes
2007-08-30 17:56     ` Nathan Lynch
2007-08-30 17:56       ` Nathan Lynch
2007-08-30 20:36     ` Joel Schopp
2007-08-30 20:36       ` Joel Schopp
2007-08-30 21:28     ` Linas Vepstas
2007-08-30 21:28       ` Linas Vepstas
2007-08-31  8:57       ` Joachim Fenkes
2007-08-31  8:57         ` Joachim Fenkes
2007-08-30 18:22 ` Arnd Bergmann
2007-08-30 18:22   ` Arnd Bergmann
2007-08-31 14:34   ` Joachim Fenkes
2007-08-31 14:34     ` Joachim Fenkes
2007-08-31 17:08     ` Arnd Bergmann [this message]
2007-08-31 17:08       ` Arnd Bergmann
2007-08-31 17:46       ` Joachim Fenkes
2007-08-31 17:46         ` Joachim Fenkes

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=200708311908.05255.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=FENKES@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=pmac@au1.ibm.com \
    --cc=raisch@de.ibm.com \
    --cc=stefan.roscher@de.ibm.com \
    --cc=themann@de.ibm.com \
    --cc=tklein@de.ibm.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 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.