linux-kernel - Re: [PWM PATCH 1/5] API to consolidate PWM devices behind a common user and kernel interface

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Wed, 03 Feb 2010 23:31:22 -0600
From:	Bill Gatliff <bgat@...lgatliff.com>
To:	H Hartley Sweeten <hartleys@...ionengravers.com>
CC:	linux-embedded@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PWM PATCH 1/5] API to consolidate PWM devices behind a common
 user and kernel interface

H Hartley Sweeten wrote:
>
> Your older patch just used printk's to output the messages.  I think the
> Oops is being caused by the dev_<level>(pwm->dev, ...).  Where is pwm->dev
> being setup?
>   

Good question!  Makes me think that it isn't...

I'm traveling back to my office at the moment, should be back in late
tomorrow or Friday a.m.  I'll look at this then.

The intention was to save the result from device_create() called from
__pwm_create_sysfs(), but I'm suspicious that the patch I posted doesn't
have that code for some reason.  My local git repo here doesn't seem to
have it.  Hmmm...

b.g.

-- 
Bill Gatliff
bgat@...lgatliff.com

--
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/