From: Seungwon Jeon <tgih.jun@samsung.com>
To: 'Dolev Raviv' <draviv@codeaurora.org>, linux-scsi@vger.kernel.org
Cc: linux-arm-msm@vger.kernel.org
Subject: RE: [PATCH V1 0/8] ufs patch siries
Date: Mon, 13 May 2013 20:50:57 +0900 [thread overview]
Message-ID: <003b01ce4fd0$219de1b0$64d9a510$%jun@samsung.com> (raw)
In-Reply-To: <1368439340-26346-1-git-send-email-draviv@codeaurora.org>
On Monday, May 13, 2013, Dolev Raviv wrote:
> This patch series clusters the latest version of all the UFS patches in the
> SCSI mailing list. It gives a stable functional base line for the UFS driver.
>
> It includes the following versions:
> > [PATCH 1/2] Documentation: devicetree: Add DT bindings for UFS host
> > controller
> > [PATCH 2/2] scsi: ufs: Fix the response UPIU length setting
> > [PATCH v4 1/6] scsi: ufs: wrap the i/o access operations
> > [PATCH v4 2/6] scsi: ufs: amend interrupt configuration
> > [PATCH v4 3/6] scsi: ufs: fix interrupt status clears
> > [PATCH v4 4/6] scsi: ufs: rework link start-up process
> > [PATCH V5 1/1] scsi: ufs: Add support for sending NOP OUT UPIU
> > [PATCH V4] scsi: ufs: Set fDeviceInit flag to initiate device
> > initialization
>
> But does not include:
> > [PATCH v4 5/6] scsi: ufs: add dme configuration primit
> > [PATCH v4 6/6] scsi: ufs: add dme control primitives
>
>
> Dolev Raviv (8):
> Documentation: devicetree: Add DT bindings for UFS host controller
> scsi: ufs: Fix the response UPIU length setting
> scsi: ufs: wrap the i/o access operations
> scsi: ufs: amend interrupt configuration
> scsi: ufs: fix interrupt status clears
> scsi: ufs: rework link start-up process
> scsi: ufs: Add support for sending NOP OUT UPIU
> scsi: ufs: Set fDeviceInit flag to initiate device initialization
It seems that you missed my first comment on previous mailing.
RE: [PATCH V1 3/8] scsi: ufs: wrap the i/o access operations
Could you check the e-mail?
If you intended to sort the patches instead of Santosh,
you should have identify the author per patch e-mail expect 8/8 which is from you.
'From: Author name <Author e-mail>' is expected in the head of e-mail.
I feel that maintainer has this role, though.
And there is need to check the base of tree for ufshcd.
' scsi: ufs: add support for query requests' is not merged finally.
I think we can talk with Santosh for those.
Thanks,
Seungwon Jeon
next prev parent reply other threads:[~2013-05-13 11:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 10:02 [PATCH V1 0/8] ufs patch siries Dolev Raviv
2013-05-13 10:02 ` [PATCH V1 1/8] Documentation: devicetree: Add DT bindings for UFS host controller Dolev Raviv
2013-05-13 10:02 ` [PATCH V1 2/8] scsi: ufs: Fix the response UPIU length setting Dolev Raviv
2013-05-13 10:02 ` [PATCH V1 3/8] scsi: ufs: wrap the i/o access operations Dolev Raviv
2013-05-13 10:02 ` [PATCH V1 4/8] scsi: ufs: amend interrupt configuration Dolev Raviv
2013-05-13 10:02 ` [PATCH V1 5/8] scsi: ufs: fix interrupt status clears Dolev Raviv
2013-05-13 10:02 ` [PATCH V1 6/8] scsi: ufs: rework link start-up process Dolev Raviv
2013-05-13 10:02 ` [PATCH V1 7/8] scsi: ufs: Add support for sending NOP OUT UPIU Dolev Raviv
2013-05-13 10:02 ` [PATCH V1 8/8] scsi: ufs: Set fDeviceInit flag to initiate device initialization Dolev Raviv
2013-05-13 11:50 ` Seungwon Jeon [this message]
2013-05-14 8:01 ` [PATCH V1 0/8] ufs patch siries Dolev Raviv
-- strict thread matches above, loose matches on Subject: below --
2013-05-12 14:23 Dolev Raviv
2013-05-12 14:22 Dolev Raviv
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='003b01ce4fd0$219de1b0$64d9a510$%jun@samsung.com' \
--to=tgih.jun@samsung.com \
--cc=draviv@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-scsi@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).