From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935026AbaEaBJG (ORCPT ); Fri, 30 May 2014 21:09:06 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:40519 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934981AbaEaBJE (ORCPT ); Fri, 30 May 2014 21:09:04 -0400 Date: Fri, 30 May 2014 16:57:20 -0700 From: Greg KH To: Kumar Gala Cc: arm@kernel.org, Kevin Hilman , Arnd Bergmann , linux-arm-msm , linux-kernel@vger.kernel.org, Olof Johansson , David Brown , linux-arm-kernel@lists.infradead.org, Andy Gross Subject: Re: [GIT PULL] qcom driver changes for v3.16-2 Message-ID: <20140530235720.GA27752@kroah.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, May 30, 2014 at 11:41:01AM -0500, Kumar Gala wrote: > The following changes since commit 5d144e36b7c51612922fa05d37ff3a869261cc82: > > soc: qcom: Add GSBI driver (2014-05-23 11:38:04 -0500) > > are available in the git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/galak/linux-qcom.git tags/qcom-drivers-for-3.16-2 > > for you to fetch changes up to 31964ffebbb958c6cf289c7c12edd7530d6221b9: > > tty: serial: msm: Remove direct access to GSBI (2014-05-29 11:06:20 -0500) > > ---------------------------------------------------------------- > Qualcomm ARM Based driver Updates for v3.16-2 > > * Updated MSM uart driver to not access GSBI control registers > > ---------------------------------------------------------------- > Andy Gross (1): > tty: serial: msm: Remove direct access to GSBI > > drivers/tty/serial/msm_serial.c | 48 ++--------------------------------------- > drivers/tty/serial/msm_serial.h | 5 ----- > 2 files changed, 2 insertions(+), 51 deletions(-) Do you want me to take these in the tty tree? Or are they going to go through the arm tree(s) for other reasons (dependancies)? thanks, greg k-h