[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 9 Sep 2014 00:47:11 +0000
From: "Chen, Alvin" <alvin.chen@...el.com>
To: "Shevchenko, Andriy" <andriy.shevchenko@...el.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"Kweh, Hock Leong" <hock.leong.kweh@...el.com>,
"sebastian@...akpoint.cc" <sebastian@...akpoint.cc>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"Ong, Boon Leong" <boon.leong.ong@...el.com>,
"gnurou@...il.com" <gnurou@...il.com>,
"linus.walleij@...aro.org" <linus.walleij@...aro.org>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"grant.likely@...aro.org" <grant.likely@...aro.org>,
"Westerberg, Mika" <mika.westerberg@...el.com>,
"dvhart@...ux.intel.com" <dvhart@...ux.intel.com>,
"atull@...nsource.altera.com" <atull@...nsource.altera.com>
Subject: RE: [PATCH 2/3 v2] GPIO: gpio-dwapb: Support Debounce
> > Since the 'debounce' feature also needs read/write, if we splite this
> > patch, then for 'debounce', One patch use readl/writel, and another
> > patch change to dwapb_read/write. It seems duplicate since the previous
> patch use readl/writel and the fllowing one change it immediately.
> > Since this patch is small, could we just make them together? How do you
> think?
>
> Make the dwapb_writel/readl patch goes first in the series.
>
OK.
Powered by blists - more mailing lists