Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753905Ab2FRWVL (ORCPT ); Mon, 18 Jun 2012 18:21:11 -0400 Received: from mail-pb0-f46.google.com ([209.85.160.46]:46337 "EHLO mail-pb0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751305Ab2FRWVI (ORCPT ); Mon, 18 Jun 2012 18:21:08 -0400 Date: Mon, 18 Jun 2012 15:21:04 -0700 From: Greg Kroah-Hartman To: Darren Hart Cc: Tomoya MORINAGA , Linux Kernel Mailing List , Feng Tang , Alexander Stein , Alan Cox , linux-serial@vger.kernel.org Subject: Re: [RFC PATCH] pch_uart: Add eg20t_port lock field, avoid recursive spinlocks Message-ID: <20120618222104.GA9543@kroah.com> References: <8854635ac5471f8671b93c65e3663eb1cb204c9d.1338454156.git.dvhart@linux.intel.com> <4FC90BAD.3080606@linux.intel.com> <4FCE8307.3050901@linux.intel.com> <4FDFA09A.4030405@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4FDFA09A.4030405@linux.intel.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 939 Lines: 27 On Mon, Jun 18, 2012 at 02:41:46PM -0700, Darren Hart wrote: > > > On 06/05/2012 04:48 PM, Tomoya MORINAGA wrote: > > On Wed, Jun 6, 2012 at 7:07 AM, Darren Hart wrote: > >> Are there still concerns about the additional lock? I'll resend V2 > >> tomorrow with the single whitespace fix if I don't hear anything back today. > > > > I understand your saying. Looks good. > > However, I am not expert of linux-uart core system. > > So, I'd like UART maintainer to give us your opinion. > > Greg, Alan, > > any concerns with the locking approach I've adopted in the patch? Care to resend the patch, as it was a RFC one, it's no longer in my queue. thanks, greg k-h -- 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/