| 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
| ||
|
Date: Thu, 04 Feb 2010 11:30:56 -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 Bill Gatliff wrote: > 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? >> >> > > 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... > No, that's not right. Disregard the above. If the PWM device in question is already known to the kernel, then before you call pwm_register() you must set pwm->dev to the address of that device structure. I need to come up with a better way to handle this. If the PWM device isn't already known to the kernel as a true struct device, then I don't yet have a Plan B. Drat. :( 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/
Powered by blists - more mailing lists