[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1342447217.3176.22.camel@dabdike.int.hansenpartnership.com>
Date: Mon, 16 Jul 2012 15:00:17 +0100
From: James Bottomley <James.Bottomley@...senPartnership.com>
To: Arnd Bergmann <arnd@...db.de>
Cc: Vinayak Holikatti <vinholikatti@...il.com>,
linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org,
patches@...aro.org, linux-samsung-soc@...r.kernel.org,
santoshsy@...il.com, arnd@...aro.org,
girish.shivananjappa@...aro.org, saugata.das@...aro.org,
vishak.g@...sung.com, venkat@...aro.org, k.rajesh@...sung.com,
dsaxena@...aro.org, ilho215.lee@...sung.com, nala.la@...sung.com,
sreekumar.c@...sung.com
Subject: Re: [PATCH V2 0/4] [SCSI] ufs: Adds glue drivers to ufshcd
On Fri, 2012-07-13 at 15:45 +0000, Arnd Bergmann wrote:
> On Friday 13 July 2012, Vinayak Holikatti wrote:
> > This patch set adds following features
> > - Seprates PCI specific code from ufshcd.c to make it as core
> > - Adds PCI glue driver ufshcd-pci.c
> > - Adds Platform glue driver ufshcd-pltfrm.c
> > - Update correct transfer size in Command UPIU
>
> Acked-by: Arnd Bergmann <arnd@...db.de>
I need a maintainer ack for this to go upstream.
Also, looking at this, I think this patch series isn't bisectable:
Patch 1 removes PCI support and patch 2 adds it back in a different
form. However, any PCI based UFS system would stop working if the
bisect landed at patch 1. I think you can fix this just by combining
patches 1 and 2.
James
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists