From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: vinayak holikatti <vinholikatti@gmail.com>
Cc: Venkatraman S <svenkatr@ti.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: Tue, 13 Nov 2012 15:26:38 -0600 [thread overview]
Message-ID: <1352841998.8317.1.camel@dabdike> (raw)
In-Reply-To: <CAKVbJB_FpmbtcLr5G5sSphNOPnodZUd0sN8ha0C_RtCDtWUG=Q@mail.gmail.com>
On Thu, 2012-10-18 at 17:37 +0530, vinayak holikatti wrote:
> 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 ?
OK, so it doesn't apply for me either:
patching file drivers/scsi/ufs/ufshcd.c
Hunk #11 FAILED at 902.
Hunk #15 succeeded at 1157 with fuzz 1 (offset 2 lines).
Hunk #16 succeeded at 1271 (offset 2 lines).
Hunk #17 succeeded at 1300 (offset 2 lines).
Hunk #18 succeeded at 1364 (offset 2 lines).
Hunk #19 succeeded at 1499 (offset 2 lines).
Hunk #20 succeeded at 1542 (offset 2 lines).
Hunk #21 succeeded at 1678 (offset 2 lines).
Hunk #22 succeeded at 1706 (offset 2 lines).
Hunk #23 succeeded at 1727 (offset 2 lines).
Hunk #24 succeeded at 1775 (offset 2 lines).
Hunk #25 succeeded at 1819 (offset 2 lines).
Hunk #26 succeeded at 1872 (offset 2 lines).
Hunk #27 succeeded at 1898 (offset 2 lines).
Hunk #28 FAILED at 2011.
2 out of 28 hunks FAILED -- saving rejects to file
drivers/scsi/ufs/ufshcd.c.rej
James
next prev parent reply other threads:[~2012-11-13 21:26 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
2012-11-13 21:26 ` James Bottomley [this message]
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=1352841998.8317.1.camel@dabdike \
--to=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=vinholikatti@gmail.com \
--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).