public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Felipe Contreras <al593181@mail.mty.itesm.mx>
Cc: linux-kernel@vger.kernel.org
Subject: Re: buffer_boundary isn't defined
Date: Mon, 24 Jun 2002 13:51:34 +1000	[thread overview]
Message-ID: <4170.1024890694@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Sun, 23 Jun 2002 22:05:10 EST." <20020624030510.GA119@zion.mty.itesm.mx>

On Sun, 23 Jun 2002 22:05:10 -0500, 
Felipe Contreras <al593181@mail.mty.itesm.mx> wrote:
>Doing some hacking I found something weird since 2.5.19, buffer_boundary and
>set_buffer_boundary are not defined, at least greping the source tree I couldn't
>find where they could be defined.
>
>The weird thing is that kbuild doesn't report that.

include/linux/buffer_head.h: BUFFER_FNS(Boundary, boundary).  Don't you
just love macros that generate names under the covers?



      reply	other threads:[~2002-06-24  3:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-24  3:05 buffer_boundary isn't defined Felipe Contreras
2002-06-24  3:51 ` Keith Owens [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=4170.1024890694@kao2.melbourne.sgi.com \
    --to=kaos@ocs.com.au \
    --cc=al593181@mail.mty.itesm.mx \
    --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