linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: vinayak holikatti <vinholikatti@gmail.com>
To: Venkatraman S <svenkatr@ti.com>
Cc: James.Bottomley@hansenpartnership.com,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	patches@linaro.org, linux-samsung-soc@vger.kernel.org,
	arnd@linaro.org, girish.shivananjappa@linaro.org,
	saugata.das@linaro.org, vishak.g@samsung.com, venkat@linaro.org,
	k.rajesh@samsung.com, dsaxena@linaro.org,
	ilho215.lee@samsung.com, nala.la@samsung.com,
	sreekumar.c@samsung.com, Santosh Yaraganavi <santoshsy@gmail.com>
Subject: Re: [PATCH V4 1/4] [SCSI] drivers/scsi/ufs: Seggregate PCI Specific Code
Date: Thu, 18 Oct 2012 17:37:01 +0530	[thread overview]
Message-ID: <CAKVbJB_FpmbtcLr5G5sSphNOPnodZUd0sN8ha0C_RtCDtWUG=Q@mail.gmail.com> (raw)
In-Reply-To: <507FA52E.9050400@ti.com>

On Thu, Oct 18, 2012 at 12:13 PM, Venkatraman S <svenkatr@ti.com> wrote:
> On Wednesday 17 October 2012 05:23 PM, Vinayak Holikatti wrote:
>>
>> This patch seggregates the PCI specific code in ufshcd.c to make it
>> ready for splitting into core ufs driver and PCI glue driver. Also
>> copyright header modification to remove extra warranty disclaim.
>>
>> Reviewed-by: Arnd Bergmann <arnd@arndb.de>
>> Reviewed-by: Namjae Jeon <linkinjeon@gmail.com>
>> Signed-off-by: Vinayak Holikatti <vinholikatti@gmail.com>
>> Signed-off-by: Santosh Yaraganavi <santoshsy@gmail.com>
>> ---
>>   drivers/scsi/ufs/Kconfig  |   50 +++----
>>   drivers/scsi/ufs/ufs.h    |   42 ++----
>>   drivers/scsi/ufs/ufshcd.c |  358
>> ++++++++++++++++++++++++++-------------------
>>   drivers/scsi/ufs/ufshci.h |   42 ++----
>>   4 files changed, 256 insertions(+), 236 deletions(-)
>>
I am Vacation will look into it when i am back to work.
> This doesn't apply on 3.7-rc1. Am I missing any patches in between ?



-- 
Regards,
Vinayak Holikatti

  reply	other threads:[~2012-10-18 12:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-17 11:53 [PATCH V4 0/4] [SCSI] ufs: Adds glue drivers to ufshcd Vinayak Holikatti
2012-10-17 11:53 ` [PATCH V4 1/4] [SCSI] drivers/scsi/ufs: Seggregate PCI Specific Code Vinayak Holikatti
2012-10-18  6:43   ` Venkatraman S
2012-10-18 12:07     ` vinayak holikatti [this message]
2012-11-13 21:26       ` James Bottomley
2012-11-21 10:32         ` vinayak holikatti
2012-11-21 10:56           ` James Bottomley
2012-11-21 12:04             ` vinayak holikatti
2012-10-17 11:53 ` [PATCH V4 2/4] [SCSI] drivers/scsi/ufs: Separate PCI code into glue driver Vinayak Holikatti
2012-10-17 11:53 ` [PATCH V4 3/4] [SCSI] ufs: Add Platform glue driver for ufshcd Vinayak Holikatti
2012-10-17 11:53 ` [PATCH V4 4/4] [SCSI] ufs: Correct the expected data transfer size Vinayak Holikatti

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAKVbJB_FpmbtcLr5G5sSphNOPnodZUd0sN8ha0C_RtCDtWUG=Q@mail.gmail.com' \
    --to=vinholikatti@gmail.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=arnd@linaro.org \
    --cc=dsaxena@linaro.org \
    --cc=girish.shivananjappa@linaro.org \
    --cc=ilho215.lee@samsung.com \
    --cc=k.rajesh@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=nala.la@samsung.com \
    --cc=patches@linaro.org \
    --cc=santoshsy@gmail.com \
    --cc=saugata.das@linaro.org \
    --cc=sreekumar.c@samsung.com \
    --cc=svenkatr@ti.com \
    --cc=venkat@linaro.org \
    --cc=vishak.g@samsung.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).