From: Michal Jaegermann <michal@harddata.com>
To: Patrick Mochel <mochel@osdl.org>
Cc: linux-kernel@vger.kernel.org, jgarzik@mandrakesoft.com
Subject: Re: kernel 2.5.20 on alpha (RE: [patch] Re: kernel 2.5.18 on alpha)
Date: Tue, 4 Jun 2002 14:23:17 -0600 [thread overview]
Message-ID: <20020604142317.B18238@mail.harddata.com> (raw)
In-Reply-To: <000101c20bd5$b8f24560$010b10ac@sbp.uptime.at> <Pine.LNX.4.33.0206040749530.654-100000@geena.pdx.osdl.net>
On Tue, Jun 04, 2002 at 08:19:49AM -0700, Patrick Mochel wrote:
>
> The short of it: 2.5.19 introduced a struct bus_type that describes each
> bus type in the system.
Which immediately collided with 'static struct bus_type {...}'
hidden in drivers/net/tulip/de4x5.c and, as result, the later does
not compile anymore. These two "bus_types" are quite dissimilar. :-)
An obvious and trivial fix was to globally replace "bus_type"
in de4x5.c with "de4x5_bus_type" (or this should be done in some
other manner).
Michal
next prev parent reply other threads:[~2002-06-04 20:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 10:11 kernel 2.5.20 on alpha (RE: [patch] Re: kernel 2.5.18 on alpha) Oliver Pitzeier
2002-06-04 12:45 ` Oliver Pitzeier
2002-06-04 14:06 ` Oliver Pitzeier
2002-06-04 14:22 ` Jan-Benedict Glaw
2002-06-04 15:13 ` Oliver Pitzeier
2002-06-04 15:47 ` Oliver Pitzeier
2002-06-04 14:40 ` Oliver Pitzeier
2002-06-04 15:19 ` Patrick Mochel
2002-06-04 15:33 ` Oliver Pitzeier
2002-06-04 20:23 ` Michal Jaegermann [this message]
2002-06-04 20:36 ` Jeff Garzik
2002-06-04 22:00 ` Paul Mackerras
2002-06-04 22:07 ` kernel 2.5.20 on alpha David S. Miller
2002-06-04 16:24 ` kernel 2.5.20 on alpha (RE: [patch] Re: kernel 2.5.18 on alpha) Thunder from the hill
2002-06-04 20:04 ` David Mosberger
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=20020604142317.B18238@mail.harddata.com \
--to=michal@harddata.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
/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.