Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755214Ab0LMHOb (ORCPT ); Mon, 13 Dec 2010 02:14:31 -0500 Received: from mail-yx0-f174.google.com ([209.85.213.174]:54297 "EHLO mail-yx0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751753Ab0LMHOa (ORCPT ); Mon, 13 Dec 2010 02:14:30 -0500 MIME-Version: 1.0 In-Reply-To: <1291933475.3271.211.camel@odin> References: <1291933475.3271.211.camel@odin> Date: Mon, 13 Dec 2010 15:14:29 +0800 Message-ID: Subject: Re: [PATCH 1/2] Change the register name definitions for mc13783 From: Yong Shen To: Liam Girdwood Cc: List Linux Arm Kernel , Mark Brown , Sascha Hauer , =?ISO-8859-1?Q?Uwe_Kleine=2DK=F6nig?= , linux-kernel@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1221 Lines: 41 Hi Liam, On Fri, Dec 10, 2010 at 6:24 AM, Liam Girdwood wrote: > On Thu, 2010-12-02 at 18:43 +0800, Yong Shen wrote: >> Hi there, >> >> Please give comments inline and use attached patch for testing. >> >> Thanks >> Yong >> >> >From e112153c6f03b49c229a8e3913a0c0459245df20 Mon Sep 17 00:00:00 2001 >> From: Yong Shen >> Date: Thu, 2 Dec 2010 14:17:02 +0800 >> Subject: [PATCH 1/2] Change the register name definitions for mc13783 >> >> To make mc13783 and mc13892 share code, the register names should be >> changed to fit the new macro definitions in the comming patch. > > I've just tried to apply this patch and looks like your mailer has > mangled parts of it. I repaired it and sadly it still does not apply > against the regulator tree. > > git://git.kernel.org/pub/scm/linux/kernel/git/lrg/voltage-2.6.git #for-next > > Can you redo, add the acks received and resubmit. Sure, I can redo it. Yong > > Thanks > > Liam > > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/