From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] trivial patch for 2.4: resolve megaraid_info name collision
Date: Sat, 18 Sep 2004 11:02:43 -0300 [thread overview]
Message-ID: <20040918140243.GB3435@logos.cnet> (raw)
In-Reply-To: <200409181702.35550.vda@port.imtp.ilyichevsk.odessa.ua>
On Sat, Sep 18, 2004 at 05:03:12PM +0300, Denis Vlasenko wrote:
> I'm not sure whether it make sense to compile in
> megaraid and megaraid2 at once,
It doesnt.
> but it does not build without this patch.
Its intentional.
next prev parent reply other threads:[~2004-09-18 17:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-16 11:28 top hogs CPU in 2.6: kallsyms_lookup is very slow Denis Vlasenko
2004-09-16 11:45 ` William Lee Irwin III
2004-09-16 11:57 ` Denis Vlasenko
2004-09-16 12:17 ` William Lee Irwin III
2004-09-16 12:31 ` Denis Vlasenko
2004-09-17 8:57 ` Denis Vlasenko
2004-09-17 11:03 ` William Lee Irwin III
2004-09-17 12:34 ` Denis Vlasenko
2004-09-17 13:33 ` William Lee Irwin III
2004-09-17 20:36 ` Denis Vlasenko
2004-09-17 21:32 ` William Lee Irwin III
[not found] ` <200409172155.29561.vda@port.imtp.ilyichevsk.odessa.ua>
2004-09-18 13:57 ` [PATCH] trivial patch for 2.4: always inline __constant_* Denis Vlasenko
2004-09-18 14:03 ` [PATCH] trivial patch for 2.4: resolve megaraid_info name collision Denis Vlasenko
2004-09-18 14:02 ` Marcelo Tosatti [this message]
2004-09-18 15:05 ` [PATCH] trivial patch for 2.4: always inline __constant_* Marcelo Tosatti
2004-09-17 9:01 ` top hogs CPU in 2.6: kallsyms_lookup is very slow Denis Vlasenko
2004-09-17 10:55 ` William Lee Irwin III
2004-09-17 11:27 ` Paulo Marques
2004-09-17 11:21 ` Denis Vlasenko
2004-09-17 12:10 ` William Lee Irwin III
2004-09-17 13:04 ` Denis Vlasenko
2004-09-17 13:55 ` Larry McVoy
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=20040918140243.GB3435@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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