Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753966Ab2FEXsX (ORCPT ); Tue, 5 Jun 2012 19:48:23 -0400 Received: from mail-pz0-f46.google.com ([209.85.210.46]:60309 "EHLO mail-pz0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753881Ab2FEXsW (ORCPT ); Tue, 5 Jun 2012 19:48:22 -0400 MIME-Version: 1.0 In-Reply-To: <4FCE8307.3050901@linux.intel.com> References: <8854635ac5471f8671b93c65e3663eb1cb204c9d.1338454156.git.dvhart@linux.intel.com> <4FC90BAD.3080606@linux.intel.com> <4FCE8307.3050901@linux.intel.com> Date: Wed, 6 Jun 2012 08:48:20 +0900 Message-ID: Subject: Re: [RFC PATCH] pch_uart: Add eg20t_port lock field, avoid recursive spinlocks From: Tomoya MORINAGA To: Darren Hart Cc: Linux Kernel Mailing List , Feng Tang , Alexander Stein , Greg Kroah-Hartman , Alan Cox , linux-serial@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: 630 Lines: 15 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. thanks. tomoya -- 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/