From: John Weber <weber@nyc.rr.com>
To: Miguel Maria Godinho de Matos <Astinus@netcabo.pt>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Loop.c File !!!!
Date: Tue, 20 Nov 2001 18:25:29 -0500 [thread overview]
Message-ID: <3BFAE669.342B268D@nyc.rr.com> (raw)
In-Reply-To: <fa.ihadquv.1knkor8@ifi.uio.no>
What version of the kernel are you trying to compile?
Miguel Maria Godinho de Matos wrote:
>
> 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.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next parent reply other threads:[~2001-11-21 2:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.ihadquv.1knkor8@ifi.uio.no>
2001-11-20 23:25 ` John Weber [this message]
2001-11-20 23:12 Loop.c File !!!! Miguel Maria Godinho de Matos
2001-11-20 20:59 ` Ryan M. McConahy
2001-11-21 1:03 ` J Sloan
2001-11-20 23:19 ` Chris Wright
2001-11-26 19:58 ` Bill Davidsen
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=3BFAE669.342B268D@nyc.rr.com \
--to=weber@nyc.rr.com \
--cc=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