From: Joel Schopp <jschopp@austin.ibm.com>
To: Joachim Fenkes <FENKES@de.ibm.com>
Cc: Thomas Q Klein <tklein@de.ibm.com>,
Jan-Bernd Themann <themann@de.ibm.com>,
Paul Mackerras <pmac@au1.ibm.com>,
LKML <linux-kernel@vger.kernel.org>,
LinuxPPC-Dev <linuxppc-dev@ozlabs.org>,
Christoph Raisch <raisch@de.ibm.com>,
Nathan Lynch <ntl@pobox.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: Thu, 30 Aug 2007 15:36:30 -0500 [thread overview]
Message-ID: <46D72A4E.6060106@austin.ibm.com> (raw)
In-Reply-To: <OF9D1ED44F.896DCCC5-ONC1257347.0044D256-C1257347.004CFB07@de.ibm.com>
> There are currently two GX devices, eHCA and eHEA, which both reside
> beneath the root node - this is required by architecture for those
> devices. Unless they invent a device called
> "supercalifragilisticexpialidocious", devices in the root note will have a
> full_name of less than 31 chars. Even in that case, the truncation occurs
> at the beginning, so the @xxx part that makes the nodes unique will stay
> in place.
>
OK, didn't realize it had to be beneath the root node, and that the
truncation truncated the front and not the back. I would have done it
differently, but this should work.
Acked-by: Joel Schopp <jschopp@austin.ibm.com>
WARNING: multiple messages have this Message-ID (diff)
From: Joel Schopp <jschopp@austin.ibm.com>
To: Joachim Fenkes <FENKES@de.ibm.com>
Cc: Nathan Lynch <ntl@pobox.com>,
Christoph Raisch <raisch@de.ibm.com>,
Jan-Bernd Themann <themann@de.ibm.com>,
LKML <linux-kernel@vger.kernel.org>,
LinuxPPC-Dev <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: Thu, 30 Aug 2007 15:36:30 -0500 [thread overview]
Message-ID: <46D72A4E.6060106@austin.ibm.com> (raw)
In-Reply-To: <OF9D1ED44F.896DCCC5-ONC1257347.0044D256-C1257347.004CFB07@de.ibm.com>
> There are currently two GX devices, eHCA and eHEA, which both reside
> beneath the root node - this is required by architecture for those
> devices. Unless they invent a device called
> "supercalifragilisticexpialidocious", devices in the root note will have a
> full_name of less than 31 chars. Even in that case, the truncation occurs
> at the beginning, so the @xxx part that makes the nodes unique will stay
> in place.
>
OK, didn't realize it had to be beneath the root node, and that the
truncation truncated the front and not the back. I would have done it
differently, but this should work.
Acked-by: Joel Schopp <jschopp@austin.ibm.com>
next prev parent reply other threads:[~2007-08-30 20:36 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 [this message]
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
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=46D72A4E.6060106@austin.ibm.com \
--to=jschopp@austin.ibm.com \
--cc=FENKES@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=ntl@pobox.com \
--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.