From: Miguel Maria Godinho de Matos <Astinus@netcabo.pt>
To: linux-kernel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Loop.c File !!!!
Date: Tue, 20 Nov 2001 23:12:02 +0000 [thread overview]
Message-ID: <EXCH01SMTP011vDfrwV0000fda4@smtp.netcabo.pt> (raw)
The problem is the following:
I AM A NEWBIE!!!
Well i had some questions about the linux kernel compilation and some of you
gave me some real goos answeres, however, there is an issue which keeps
buzzing my head and that i can't understand!
Some one told me i should edit the loop.c file and even tried to explained me
why but i couldn't understand.
He said something about my new kernel wouldn't be able to compile if two or
three lines weren't comented!
I didn't understand this fact so i would like to know why should i edit the
/usr/src/linux/drivers/block/loop.c file!!!!
Plz some one explain me this fact.
tks for your attention, Astinus
If i wasn't explicit enough plz tell me! So i can reformulate my e-mail post!
once again tks for your attention.
next reply other threads:[~2001-11-20 23:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-20 23:12 Miguel Maria Godinho de Matos [this message]
2001-11-20 20:59 ` Ryan M. McConahy
2001-11-21 1:03 ` J Sloan
2001-11-21 7:28 ` Linux FSCP (Frequently Submitted Compilation Problems)? (was: Re: Loop.c File !!!!) DevilKin
2001-11-21 8:57 ` Matt Bernstein
2001-11-21 9:10 ` Rob Turk
2001-11-21 23:18 ` Stuart Young
2001-11-22 7:07 ` Rob Turk
2001-11-23 0:03 ` Stuart Young
2001-11-23 1:03 ` Andreas Dilger
2001-11-23 1:16 ` Richard Gooch
2001-11-23 1:20 ` Arnaldo Carvalho de Melo
2001-11-23 1:45 ` Richard Gooch
2001-11-23 4:22 ` Andreas Dilger
2001-11-23 4:40 ` Keith Owens
2001-11-23 4:38 ` Richard Gooch
2001-11-23 7:10 ` Rob Turk
2001-11-23 20:18 ` Mike Fedyk
2001-11-20 23:19 ` Loop.c File !!!! Chris Wright
2001-11-26 19:58 ` Bill Davidsen
[not found] <fa.ihadquv.1knkor8@ifi.uio.no>
2001-11-20 23:25 ` John Weber
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=EXCH01SMTP011vDfrwV0000fda4@smtp.netcabo.pt \
--to=astinus@netcabo.pt \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®