From: Christoph Hellwig <hch@infradead.org>
To: Dolev Raviv <draviv@codeaurora.org>
Cc: james.bottomley@hansenpartnership.com,
linux-scsi@vger.kernel.org, linux-arm-msm@vger.kernel.org,
santoshsy@gmail.com
Subject: Re: [PATCH 0/6] various fixes for UFS-PM series
Date: Fri, 24 Oct 2014 02:22:51 -0700 [thread overview]
Message-ID: <20141024092251.GA22849@infradead.org> (raw)
In-Reply-To: <cf3edc6781220b166188fb5f6d07cc2d.squirrel@www.codeaurora.org>
On Fri, Oct 24, 2014 at 07:53:23AM -0000, Dolev Raviv wrote:
> The first patch is Akinobu Mita's patch.
> You can add my ack on it.
Given that you passed them on to me you should normally sign off on them
as well.
Btw, MAINTAINERS doesn't mention you for the ufs driver, should it?
next prev parent reply other threads:[~2014-10-24 9:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-23 10:25 [PATCH 0/6] various fixes for UFS-PM series Dolev Raviv
2014-10-23 10:25 ` [PATCH 1/6] scsi: ufs: fix reference counting of W-LUs Dolev Raviv
2014-10-23 10:25 ` [PATCH 2/6] scsi: ufs: fix power info after link start-up Dolev Raviv
2014-10-23 10:25 ` [PATCH 3/6] scsi: ufs: fix static checker errors in ufshcd_system_suspend Dolev Raviv
2014-10-23 10:25 ` [PATCH 4/6] scsi: ufs: fix static checker warning in ufshcd_populate_vreg Dolev Raviv
2014-10-23 10:25 ` [PATCH 5/6] scsi: ufs: fix static checker warning in __ufshcd_setup_clocks Dolev Raviv
2014-10-23 10:25 ` [PATCH 6/6] scsi: ufs: fix static checker warning in ufshcd_parse_clock_info Dolev Raviv
2014-10-23 17:15 ` [PATCH 0/6] various fixes for UFS-PM series Christoph Hellwig
2014-10-24 7:53 ` Dolev Raviv
2014-10-24 9:22 ` Christoph Hellwig [this message]
2014-10-26 11:04 ` Dolev Raviv
2014-10-27 9:50 ` Christoph Hellwig
2014-11-20 11:19 ` Dolev Raviv
2014-11-20 11:42 ` merez
2014-11-20 16:48 ` Christoph Hellwig
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=20141024092251.GA22849@infradead.org \
--to=hch@infradead.org \
--cc=draviv@codeaurora.org \
--cc=james.bottomley@hansenpartnership.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=santoshsy@gmail.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