public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Roger W. Brown" <bregor@anusf.anu.edu.au>
To: linux-kernel@vger.kernel.org
Cc: axobe@suse.de, akpm@zip.com.au
Subject: Re: Definition conflict in 2.4.19-pre?? code
Date: Wed, 5 Jun 2002 22:03:38 +1000	[thread overview]
Message-ID: <200206052203.38253.bregor@sf.anu.edu.au> (raw)
In-Reply-To: <200206051736.45920.bregor@sf.anu.edu.au> <20020605100229.GX1105@suse.de>


                  (  Original message deleted )
>
> Your kernel tree must be corrupted, there's no such change in later
> 2.4.19-pre. pre10 still uses two request wait queues.

  Yes indeed !!   My patch program trips and falls whenever it encounters the    
line: "\ No newline at end of file"   I hadn't noticed.  Sorry.

-- 
Roger Brown 

      reply	other threads:[~2002-06-05 12:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-05  7:36 Definition conflict in 2.4.19-pre?? code Roger W. Brown
2002-06-05 10:02 ` Jens Axboe
2002-06-05 12:03   ` Roger W. Brown [this message]

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=200206052203.38253.bregor@sf.anu.edu.au \
    --to=bregor@anusf.anu.edu.au \
    --cc=akpm@zip.com.au \
    --cc=axobe@suse.de \
    --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