linux-kernel - Re: [PATCH 0/3] Add GPIO support for the MAX6650/6651 ICs

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: <CAOMwXhN7JzCZZVtNTHPAhrdFkM4z10J634ctBPR2u+tRUOtSqw@mail.gmail.com>
Date:	Wed, 8 Jan 2014 17:07:24 +0000
From:	Laszlo Papp <lpapp@....org>
To:	Lee Jones <lee.jones@...aro.org>
Cc:	Guenter Roeck <linux@...ck-us.net>,
	Linus Walleij <linus.walleij@...aro.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/3] Add GPIO support for the MAX6650/6651 ICs

In other words, I really do not know what format you prefer for design review.

Apparently, not as previously requested, so please tell me what format
one _should_ submit design reviews in.

I personally still think that submitting "pseudo-code" is a good way
of it if it is clearly marked so like in my case, so that it does not
mislead anyone that I accidentally submit a clearly broken change for
an integration candidate.

I hope it is understood that I am asking about design reviews before
the lengthy implementation to potentially avoid a lot of additional
work on both sides with writing and reviewing an implementation with a
"wrong" approach...

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