From mboxrd@z Thu Jan 1 00:00:00 1970 From: Grant Likely Subject: Re: [PATCH v3 00/13] gpio/omap: Some more driver cleanup and fixes Date: Mon, 12 Mar 2012 21:57:28 -0600 Message-ID: <20120313035728.B56993E0FAA@localhost> References: <1331118963-26364-1-git-send-email-tarun.kanti@ti.com> <878vj5y7iv.fsf@ti.com> <87vcm9v4h1.fsf@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <87vcm9v4h1.fsf@ti.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-arm-kernel-bounces@lists.infradead.org Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Kevin Hilman , "DebBarma, Tarun Kanti" Cc: tony@atomide.com, linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org List-Id: linux-omap@vger.kernel.org On Mon, 12 Mar 2012 15:28:42 -0700, Kevin Hilman wrote: > "DebBarma, Tarun Kanti" writes: > > [...] > > >>> Oops... I am sorry. > >>> I was in the process of updating the branch with latest comments after > >>> base-lining on Grant's: > >>> git://git.secretlab.ca/git/linux-2.6.git > >>> Branch: gpio/next > >>> Because this has all the gpio changes including Benoit's latest gpio > >>> devicetree changes. > >>> Should I go ahead? > >> Anyways, for the time being I am updating on top of your changes as before. > >> You should be able to see the branch shortly. > > Please note that the branch has your following patch: > > gpio/omap: fix wakeups on level-triggered GPIOs > > Please be sure to Cc the GPIO maintainer (added now.) > > Grant can we consider your gpio/next a stable baseline for further > GPIO fixes? > > If so, Tarun, please base your branch there. Otherwise, continue to use > my for_3.4/gpio/runtime-pm-cleanup, but please test it by merging with > the gpio/next branch. I'm not going to rebase gpio/next before the merge window; you can base on it with confidence. g. From mboxrd@z Thu Jan 1 00:00:00 1970 From: grant.likely@secretlab.ca (Grant Likely) Date: Mon, 12 Mar 2012 21:57:28 -0600 Subject: [PATCH v3 00/13] gpio/omap: Some more driver cleanup and fixes In-Reply-To: <87vcm9v4h1.fsf@ti.com> References: <1331118963-26364-1-git-send-email-tarun.kanti@ti.com> <878vj5y7iv.fsf@ti.com> <87vcm9v4h1.fsf@ti.com> Message-ID: <20120313035728.B56993E0FAA@localhost> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Mon, 12 Mar 2012 15:28:42 -0700, Kevin Hilman wrote: > "DebBarma, Tarun Kanti" writes: > > [...] > > >>> Oops... I am sorry. > >>> I was in the process of updating the branch with latest comments after > >>> base-lining on Grant's: > >>> git://git.secretlab.ca/git/linux-2.6.git > >>> Branch: gpio/next > >>> Because this has all the gpio changes including Benoit's latest gpio > >>> devicetree changes. > >>> Should I go ahead? > >> Anyways, for the time being I am updating on top of your changes as before. > >> You should be able to see the branch shortly. > > Please note that the branch has your following patch: > > gpio/omap: fix wakeups on level-triggered GPIOs > > Please be sure to Cc the GPIO maintainer (added now.) > > Grant can we consider your gpio/next a stable baseline for further > GPIO fixes? > > If so, Tarun, please base your branch there. Otherwise, continue to use > my for_3.4/gpio/runtime-pm-cleanup, but please test it by merging with > the gpio/next branch. I'm not going to rebase gpio/next before the merge window; you can base on it with confidence. g.