linux-kernel - MMC core debugfs support (was Re: [RFC v2 5/5] Atmel MCI: Driver for Atmel on-chip MMC controllers)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 14 Feb 2008 15:00:05 +0100
From:	Haavard Skinnemoen <hskinnemoen@...el.com>
To:	Pierre Ossman <drzeus-list@...eus.cx>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: MMC core debugfs support (was Re: [RFC v2 5/5] Atmel MCI: Driver
 for Atmel on-chip MMC controllers)

[removing lots of people from Cc]

On Wed, 13 Feb 2008 19:30:51 +0100
Pierre Ossman <drzeus-list@...eus.cx> wrote:

> > +static int req_dbg_open(struct inode *inode, struct file *file)
> > +{  
> 
> And this should go into the core.

I've started working on this, but I've run into a problem: The mmc core
structures don't seem to keep any references to the current request. So
I don't really have any information to put into the 'req' file after
moving it into the core.

Any ideas on how to solve this?

Haavard
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/