From: Christoph Hellwig <hch@infradead.org>
To: Subhash Jadavani <subhashj@codeaurora.org>
Cc: 'Dolev Raviv' <draviv@codeaurora.org>,
James.Bottomley@HansenPartnership.com, hch@infradead.org,
linux-scsi@vger.kernel.org, linux-arm-msm@vger.kernel.org,
santoshsy@gmail.com
Subject: Re: [PATCH 1/1] ufs: scsi: fix sparse errors in ufshcd_system_suspend
Date: Sat, 11 Oct 2014 04:06:29 -0700 [thread overview]
Message-ID: <20141011110629.GA9161@infradead.org> (raw)
In-Reply-To: <000301cfe0ed$e5221200$af663600$@codeaurora.org>
On Sun, Oct 05, 2014 at 03:44:16PM -0700, Subhash Jadavani wrote:
> Looks good, Reviewed-by: Subhash Jadavani <subhashj@codeaurora.org>
I'm getting a bit lost with all the UFS fixes, can you prepared a series
with all the fixups required for 3.18 for me please?
next prev parent reply other threads:[~2014-10-11 11:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-05 14:10 [PATCH 1/1] ufs: scsi: fix sparse errors in ufshcd_system_suspend Dolev Raviv
2014-10-05 22:44 ` Subhash Jadavani
2014-10-11 11:06 ` Christoph Hellwig [this message]
2014-10-21 14:05 ` Christoph Hellwig
2014-10-21 18:50 ` Subhash Jadavani
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=20141011110629.GA9161@infradead.org \
--to=hch@infradead.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=draviv@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=santoshsy@gmail.com \
--cc=subhashj@codeaurora.org \
/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