From: Alexey Dobriyan <adobriyan@gmail.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Jaswinder Singh Rajput <jaswinder@kernel.org>,
reiserfs-devel@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: usr/include/linux/reiserfs_fs.h is having lot of KERNEL data
Date: Sat, 24 Jan 2009 21:42:16 +0300 [thread overview]
Message-ID: <20090124184216.GA7559@x200.localdomain> (raw)
In-Reply-To: <20090124074313.GA31882@uranus.ravnborg.org>
On Sat, Jan 24, 2009 at 08:43:13AM +0100, Sam Ravnborg wrote:
> > >
> > > -/* debug levels. Right now, CONFIG_REISERFS_CHECK means print all debug
> > > -** messages.
> > > -*/
> > > +/* debug levels. Right now, REISERFS_CHECK means print all debug messages */
> >
> > Whoa, fix the tool!
>
> This comment does not make sense in userspace so the tool was right - no?
Well, one could argue why tool pays attention to comments.
Anyway, this file requires line-by-line checking and making sure reiserfstools
continues to build.
prev parent reply other threads:[~2009-01-24 18:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 15:27 usr/include/linux/reiserfs_fs.h is having lot of KERNEL data Jaswinder Singh Rajput
2009-01-24 6:35 ` Jaswinder Singh Rajput
2009-01-24 7:32 ` Alexey Dobriyan
2009-01-24 7:43 ` Sam Ravnborg
2009-01-24 18:42 ` Alexey Dobriyan [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=20090124184216.GA7559@x200.localdomain \
--to=adobriyan@gmail.com \
--cc=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-devel@vger.kernel.org \
--cc=sam@ravnborg.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