All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Dave Jones <davej@redhat.com>, Roland Dreier <roland@topspin.com>,
	linux-kernel@vger.kernel.org, openib-general@openib.org
Subject: Re: debugfs directory structure
Date: Wed, 12 Jan 2005 13:41:08 -0800	[thread overview]
Message-ID: <20050112214108.GA13801@kroah.com> (raw)
In-Reply-To: <20050112210945.GN24518@redhat.com>

On Wed, Jan 12, 2005 at 04:09:45PM -0500, Dave Jones wrote:
> On Wed, Jan 12, 2005 at 12:50:51PM -0800, Roland Dreier wrote:
>  > Hi Greg,
>  > 
>  > Now that debugfs is merged into Linus's tree, I'm looking at using it
>  > to replace the IPoIB debugging pseudo-filesystem (ipoib_debugfs).  Is
>  > there any guidance on what the structure of debugfs should look like?
>  > Right now I'm planning on putting all the debug info files under an
>  > ipoib/ top level directory.  Does that sound reasonable?
> 
> How about mirroring the toplevel kernel source structure ?
> 
> Ie, you'd make drivers/infiniband/ulp/ipoib ?

But who would be in charge of createing the "drivers/" subdirectory?

debugfs can't handle "/" in a directory name, like procfs does.

> It could get ugly quickly without some structure at least to
> the toplevel dir.

I say ipoib/ is fine, remember, this is for debugging stuff, it will
quickly get ugly anyway :)

thanks,

greg k-h

  reply	other threads:[~2005-01-12 21:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-12 20:50 debugfs directory structure Roland Dreier
2005-01-12 21:01 ` Greg KH
2005-01-12 21:09 ` Dave Jones
2005-01-12 21:41   ` Greg KH [this message]
2005-01-12 22:01     ` Dave Jones
2005-01-12 22:16       ` 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=20050112214108.GA13801@kroah.com \
    --to=greg@kroah.com \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openib-general@openib.org \
    --cc=roland@topspin.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.