From: carbonated beverage <ramune@net-ronin.org>
To: Alex Goddard <agoddard@purdue.edu>
Cc: Brad Tilley <rtilley@vt.edu>, linux-kernel@vger.kernel.org
Subject: Re: 2.5.53 make modules_install problem
Date: Fri, 27 Dec 2002 15:43:42 -0800 [thread overview]
Message-ID: <20021227234342.GA4025@net-ronin.org> (raw)
In-Reply-To: <Pine.LNX.4.50L0.0212271751380.1209-100000@dust.ebiz-gw.wintek.com>
On Fri, Dec 27, 2002 at 05:56:17PM +0000, Alex Goddard wrote:
> I don't mean that as a flame or anything. But if whatever problem you're
> having has already been discussed, and addressed before, a little research
> on your part will get you your answer more quickly than waiting for
> someone on the lkml to answer it (which may never happen).
Of course, updating Documentation/Changes would help, too. :)
See patches I've posted. :)
<speaking too soon>
(I've gotten *one* bit of feedback on it, so I'm asusming no protest means
no problems.)
</speaking too soon>
-- DN
Daniel
next prev parent reply other threads:[~2002-12-27 23:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-27 14:58 2.5.53 make modules_install problem Brad Tilley
2002-12-27 17:56 ` Alex Goddard
2002-12-27 23:43 ` carbonated beverage [this message]
2002-12-28 6:42 ` khromy
2002-12-28 2:45 ` Brad Tilley
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=20021227234342.GA4025@net-ronin.org \
--to=ramune@net-ronin.org \
--cc=agoddard@purdue.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=rtilley@vt.edu \
/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.