public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Alexander Nyberg <alexn@dsv.su.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] debugfs for 2.6.10-rc3
Date: Thu, 16 Dec 2004 16:58:06 -0800	[thread overview]
Message-ID: <20041217005806.GA12339@kroah.com> (raw)
In-Reply-To: <1103244459.1197.15.camel@boxen>

On Fri, Dec 17, 2004 at 01:47:39AM +0100, Alexander Nyberg wrote:
> On Thu, 2004-12-16 at 13:36 -0800, Greg KH wrote:
> > I've added debugfs to my bk driver tree (located at
> > bk://kernel.bkbits.net/gregkh/linux/driver-2.6) so it will show up in
> > the next -mm release.  For those who want to see the patch version, or
> > want to put it in any other kernel tree (Fedora perhaps?) I've included
> > it below.  I haven't added the kobject interface yet, I'll try to get to
> > that next week.
> > 
> > thanks,
> > 
> > greg k-h
> > 
> > ----------------------------
> > 
> > debugfs: add debugfs
> > 
> > debugfs is a filesystem that is just for debug data.
> > Start moving stuff out of proc and sysfs now :)
> 
> Hi Greg
> 
> Is there any reason why this shouldn't be buildable as module? I saw no
> apparent reason and added "|| defined(MODULE)" to debugfs.h and made the
> Kconfig option tristate. This allowed it to be built as a working module
> (yay, i didn't have to restart to try it out!).

If debugfs calls are used by any code that is built into the kernel,
then the build would fail if debugfs is a module.  As that would soon
get _real_ messy from a Kbuild standpoint, I took the easy way out and
just made it a Y/N type option :)

> Also I saw there was no debugfs_create_u64() for us on 64bit machines ;)

If you have a need for it, I'll be glad to add it :)

thanks,

greg k-h

  reply	other threads:[~2004-12-17  1:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-16 21:36 [PATCH] debugfs for 2.6.10-rc3 Greg KH
2004-12-17  0:47 ` Alexander Nyberg
2004-12-17  0:58   ` Greg KH [this message]
2004-12-18  2:33 ` Theodore Ts'o
2004-12-18  2:57   ` Greg KH

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=20041217005806.GA12339@kroah.com \
    --to=greg@kroah.com \
    --cc=alexn@dsv.su.se \
    --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