[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACRpkdYFDPG9SxtMbX21_VUZBCShCVw6TJTdswmVNXhZ051dsA@mail.gmail.com>
Date: Fri, 27 Mar 2015 09:32:39 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Sonic Zhang <sonic.adi@...il.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Grant Likely <grant.likely@...aro.org>,
Steven Miao <realmz6@...il.com>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
adi-buildroot-devel@...ts.sourceforge.net,
Sonic Zhang <sonic.zhang@...log.com>
Subject: Re: [PATCH] pinmux: allow exlusive pin allocation among GPIO and
peripheral funtions via flag strict in struct pinctrl_desc
On Thu, Mar 19, 2015 at 11:06 AM, Sonic Zhang <sonic.adi@...il.com> wrote:
> Anyway, if you think doing the explicit check in both if() and else()
> clauses is better, I am fine to send a new patch.
I looked at it for half an hour and could not figure out if it was
wrong or right really, eventually maybe got it wrong, maybe right.
What is happening is that the code is getting so convoluted that I cannot
follow the program flow, which is a clear sign that refactoring is needed.
Either restructure, add comments or break our helper functions.
Yours,
Linus Walleij
--
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