linux-kernel - Re: [PATCH 4/4] staging: et131x: Update TODO list

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]

Message-ID: <CANK3SE1tdJm93BK+U01Ep7Q2B=+aUJmgxkrQ537oPrqB2YZ4nA@mail.gmail.com>
Date:	Tue, 11 Oct 2011 17:25:47 +0100
From:	Mark Einon <mark.einon@...il.com>
To:	Greg KH <gregkh@...e.de>
Cc:	Ramesh R <rshlinux@...il.com>, devel@...verdev.osuosl.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 4/4] staging: et131x: Update TODO list

On 11 October 2011 17:11, Greg KH <gregkh@...e.de> wrote:
> On Tue, Oct 11, 2011 at 09:00:35AM -0700, Ramesh R wrote:
>> Hi Mark,
>>
>> I wish to contribute to this project - From the latest TODO list in
>> the README document
>>
>> drivers/staging/et131x/README
>>
>> If I were to start with the coding style cleanups, is there a coding
>> standard available for reference? Please advice.
>
> Documentation/CodingStyle
>
Ramesh,

There are no significant coding style issues with this particular
driver at this time, as far as I (and the checkpatch script) are aware
of.
I suggest you check other staging/ drivers for these sorts of issues.

Cheers,

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