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] [day] [month] [year] [list]
Message-ID: <6ED8E3B22081A4459DAC7699F3695FB71D723213@SW-EX-MBX02.diasemi.com>
Date:	Tue, 6 Aug 2013 13:09:56 +0000
From:	Steve Twiss <stwiss.opensource@...semi.com>
To:	Mark Brown <broonie@...nel.org>
CC:	Liam Girdwood <lgirdwood@...il.com>,
	David Dajun Chen <david.chen@...semi.com>,
	Guennadi Liakhovetski <g.liakhovetski@....de>,
	LKML <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH V1] DA9210 driver files

On Mon 15 July 2013 17:58 Mark Brown wrote:

>Subject: Re: [PATCH V1] DA9210 driver files

I should have named this PATCH V3 to follow on from previous versions
from RFC that I submitted. 

>To repeat *again* you should submit patches in the format covered in
>SubmittingPatches.  This includes things like the commit message, if
>your commit message doesn't look like other commit messages for the code
>you're changing that's an issue.

Apologies again.
I will try to make this identical to those provided in other commit 
messages ...

>
>> +struct da9210 {
>> +	struct device *dev;
>
>This is never used as far as I can tell.
>

Not used.. removed.

>> +MODULE_ALIAS("platform: da9210");
>
>This is for a platform device but this is an I2C device so would never
>match.  Also for a platform device the string should have no space in
>it.
>

Done this.
I will re-submit this asap.

>Otherwise this looks OK, though it'd be better to fill in the register
>map information more (listing the valid registers for example).

Thank you,
Steve
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ