From: tytso@mit.edu
To: Jan Kara <jack@suse.cz>
Cc: Christoph Egger <siccegge@stud.informatik.uni-erlangen.de>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Kazuo Moriwaka <moriwaka@redhat.com>,
H Hartley Sweeten <hsweeten@visionengravers.com>,
Joel Becker <joel.becker@oracle.com>,
linux-ext4@vger.kernel.org, vamos@i4.informatik.uni-erlangen.de
Subject: Re: [PATCH] obsolete config in kernel source (BUFFER_DEBUG)
Date: Mon, 8 Feb 2010 10:50:31 -0500 [thread overview]
Message-ID: <20100208155031.GK4494@thunk.org> (raw)
In-Reply-To: <20100208135629.GD4321@quack.suse.cz>
On Mon, Feb 08, 2010 at 02:56:29PM +0100, Jan Kara wrote:
> On Fri 05-02-10 14:13:33, Christoph Egger wrote:
> > Hi all!
> >
> > As part of the VAMOS[0] research project at the University of
> > Erlangen we're checking referential integrity between kernel KConfig
> > options and in-code Conditional blocks.
> >
> > With some commit somewhere around 2.4.15 the last hint of
> > CONFIG_BUFFER_DEBUG (apart from the 2 occurences this patch addresses)
> > -- some documentation -- was removed from the kernel source. However
> > this one piece of code made it till today. Time to go forward and
> > remove it?
> >
> > Please keep me informed of this patch getting confirmed /
> > merged so we can keep track of it.
> Thanks, the patch looks good. I've merged it into my linux-fs tree and
> will send it to Linus in the next merge window.
I don't have an objection with removing this, but does anyone have the
latest version of akpm's buffer debugging patches?
I *think* what happened is that akpm forward ported the removed buffer
debugging patches, or maybe rewrote it from scratch, but for whatever
reason they never made back into mainline. Maybe they were too ugly
to live in mainline, but they have been really handy on occasion.
- Ted
next prev parent reply other threads:[~2010-02-08 15:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 13:13 [PATCH] obsolete config in kernel source (BUFFER_DEBUG) Christoph Egger
2010-02-08 13:56 ` Jan Kara
2010-02-08 15:50 ` tytso [this message]
2010-02-08 18:58 ` Andrew Morton
2010-02-08 19:02 ` Eric Sandeen
-- strict thread matches above, loose matches on Subject: below --
2010-02-05 13:35 Christoph Egger
2010-02-05 15:18 ` James Bottomley
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=20100208155031.GK4494@thunk.org \
--to=tytso@mit.edu \
--cc=akpm@linux-foundation.org \
--cc=hsweeten@visionengravers.com \
--cc=jack@suse.cz \
--cc=joel.becker@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=moriwaka@redhat.com \
--cc=siccegge@stud.informatik.uni-erlangen.de \
--cc=vamos@i4.informatik.uni-erlangen.de \
/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