public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
Cc: Pierre Ossman <drzeus-mmc@drzeus.cx>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] mmc: Export ios settings for a host through debugfs
Date: Sat, 28 Jun 2008 08:33:10 -0700	[thread overview]
Message-ID: <20080628153309.GC11018@kroah.com> (raw)
In-Reply-To: <20080628160752.0fe19753@hskinnemo-gx745.norway.atmel.com>

On Sat, Jun 28, 2008 at 04:07:52PM +0200, Haavard Skinnemoen wrote:
> Pierre Ossman <drzeus-mmc@drzeus.cx> wrote:
> > On Sat, 28 Jun 2008 15:47:00 +0200
> > Haavard Skinnemoen <haavard.skinnemoen@atmel.com> wrote:
> > 
> > > Pierre Ossman <drzeus-mmc@drzeus.cx> wrote:
> > > > 
> > > > Can't we use debugfs' own bookkeeping to keep track of them? Saves us a
> > > > lot of noise in these structures.
> > > 
> > > You mean d_subdirs in struct dentry? I guess we could do that...though
> > > I was sort of trying not to dig too deply into VFS internals...
> > > 
> > 
> > I'm a complete noob when it comes to debugfs. There isn't some
> > recursive delete function that can be used on the "ios" node?
> 
> I don't think so, but I think it would be very useful. I sometimes
> forget to remove an entry so that I have to reboot in order to get my
> driver's debugfs interface going again..
> 
> Greg, do you have any suggestions?

Someone can add a "debugfs_rm_dentry_and_children" function if they so
desire to handle this kind of thing if they want to :)

thanks,

greg k-h

  reply	other threads:[~2008-06-28 15:36 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-26 11:09 [PATCH 1/3] mmc: Export internal host state through debugfs Haavard Skinnemoen
2008-06-26 11:09 ` [PATCH 2/3] mmc: Export ios settings for a host " Haavard Skinnemoen
2008-06-26 11:09   ` [PATCH 3/3] mmc: Add per-card debugfs support Haavard Skinnemoen
2008-06-28 13:37     ` Pierre Ossman
2008-06-28 13:48       ` Haavard Skinnemoen
2008-06-28 14:01         ` Pierre Ossman
2008-06-28 14:15           ` Haavard Skinnemoen
2008-06-28 15:22             ` Pierre Ossman
2008-06-28 15:36               ` Haavard Skinnemoen
2008-06-28 16:11                 ` Pierre Ossman
2008-06-28 13:34   ` [PATCH 2/3] mmc: Export ios settings for a host through debugfs Pierre Ossman
2008-06-28 13:47     ` Haavard Skinnemoen
2008-06-28 13:59       ` Pierre Ossman
2008-06-28 14:07         ` Haavard Skinnemoen
2008-06-28 15:33           ` Greg KH [this message]
2008-06-28 16:08             ` Haavard Skinnemoen
2008-06-28 16:37               ` Haavard Skinnemoen
2008-06-28 16:43                 ` Greg KH
2008-06-28 17:02                   ` Haavard Skinnemoen
2008-06-28 13:28 ` [PATCH 1/3] mmc: Export internal host state " Pierre Ossman
2008-06-28 13:37   ` Haavard Skinnemoen
2008-06-28 13:40     ` Pierre Ossman
2008-06-28 13:49       ` Haavard Skinnemoen
2008-06-28 14:23       ` Haavard Skinnemoen
2008-06-28 14:41         ` Haavard Skinnemoen
2008-06-28 15:17           ` Pierre Ossman

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=20080628153309.GC11018@kroah.com \
    --to=greg@kroah.com \
    --cc=drzeus-mmc@drzeus.cx \
    --cc=haavard.skinnemoen@atmel.com \
    --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