From: Seungwon Jeon <tgih.jun@samsung.com>
To: 'James Bottomley' <James.Bottomley@HansenPartnership.com>,
'Santosh Y' <santoshsy@gmail.com>
Cc: linux-scsi@vger.kernel.org, 'Vinayak Holikatti' <vinholikatti@gmail.com>
Subject: RE: [PATCH v4 1/6] scsi: ufs: wrap the i/o access operations
Date: Fri, 10 May 2013 10:52:34 +0900 [thread overview]
Message-ID: <000001ce4d21$0ac00920$20401b60$%jun@samsung.com> (raw)
In-Reply-To: <1368109310.1966.3.camel@dabdike>
On Thursday, May 09, 2013, James Bottomley wrote:
> On Thu, 2013-05-09 at 12:22 +0530, Santosh Y wrote:
> > On Thu, May 9, 2013 at 12:09 PM, Seungwon Jeon <tgih.jun@samsung.com> wrote:
> > > On Thursday, May 09, 2013 Santosh wrote:
> > >> > There are two patches remained. These are applied with your final comments.
> > >> > Do you have any idea?
> > >> > [PATCH v4 5/6] scsi: ufs: add dme configuration primitives
> > >> > [PATCH v4 6/6] scsi: ufs: add dme control primitives
> > >> >
> > >>
> > >> Since there is no use case for these implementations yet, except for
> > >> ufshcd_get_dme_attr_val(), as per James's suggestion
> > >> [http://www.mail-archive.com/linux-scsi@vger.kernel.org/msg20207.html]
> > >> I did not ACK the patches.
> > >> The same patches can be used to implement related features and resubmit later.
> > > I respect your decision. But I have another opinion.
> > > The remained patches are basic operations which should be supported by ufshcd.
> > > Especially, dme_set/set will be used in vender specific part of host controller rather than in
> ufshcd itself.
> > > And above all, Maya Erez completed to test and reported working fine.
> > > If these patches are merged this time, it would be helpful to various hosts.
> > >
> >
> > I'm ok with merging these patches if James is fine with it. I will ACK
> > the patches.
>
> Well, no, not really. The rule is simple: we don't add new functions to
> the kernel without callers. The reason is also simple: trying to do
> interface first and then user some time later is a "make work"
> development strategy that practically guarantees the interface is either
> never used or needs modification. From the kernel's point of view,
> which is more important, review of a function with no callers is only
> partial because you've no idea how it will be used. Whereas if you
> review a function and its callers, you can see how the API works and
> possibly suggest improvements.
Thank you for your feedback.
Okay, it will be reintroduced with actual usage soon.
Could you pick the remains except [5/6, 6/6] into your tree?
The following patches include Santosh's ack.
[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
Thanks,
Seungwon Jeon
>
> James
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-05-10 1:52 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 14:14 [PATCH 1/1] scsi: ufs: Add support for sending NOP OUT UPIU Sujit Reddy Thumma
2013-04-24 16:06 ` [PATCH 1/5] scsi: ufs: move the ufshcd_hba_stop to ufshcd.c Seungwon Jeon
2013-04-30 11:17 ` Subhash Jadavani
2013-05-01 7:46 ` merez
2013-05-02 8:11 ` Santosh Y
2013-05-02 13:37 ` Seungwon Jeon
2013-05-02 18:49 ` merez
2013-05-04 8:45 ` [PATCH v2 1/7] " Seungwon Jeon
2013-05-05 11:22 ` merez
2013-05-06 3:05 ` Seungwon Jeon
2013-05-06 5:37 ` [PATCH v3 1/6] scsi: ufs: wrap the i/o access operations Seungwon Jeon
2013-05-06 10:37 ` merez
2013-05-06 19:30 ` Santosh Y
2013-05-07 3:52 ` Seungwon Jeon
2013-05-06 5:37 ` [PATCH v3 2/6] scsi: ufs: amend interrupt configuration Seungwon Jeon
2013-05-06 10:39 ` merez
2013-05-06 5:37 ` [PATCH v3 3/6] scsi: ufs: fix interrupt status clears Seungwon Jeon
2013-05-06 10:49 ` merez
2013-05-06 5:37 ` [PATCH v3 4/6] scsi: ufs: rework link start-up process Seungwon Jeon
2013-05-06 9:47 ` Sujit Reddy Thumma
2013-05-06 10:36 ` merez
2013-05-06 11:21 ` Seungwon Jeon
2013-05-06 18:15 ` merez
2013-05-06 5:37 ` [PATCH v3 5/6] scsi: ufs: add dme configuration primitives Seungwon Jeon
2013-05-06 19:43 ` Santosh Y
2013-05-06 5:39 ` [PATCH v3 6/6] scsi: ufs: add dme control primitives Seungwon Jeon
2013-05-06 19:51 ` Santosh Y
2013-05-07 3:45 ` Seungwon Jeon
2013-05-08 8:41 ` [PATCH v4 1/6] scsi: ufs: wrap the i/o access operations Seungwon Jeon
2013-05-08 11:58 ` merez
2013-05-08 15:18 ` Santosh Y
2013-05-09 1:59 ` Seungwon Jeon
2013-05-09 3:27 ` Santosh Y
2013-05-09 6:39 ` Seungwon Jeon
2013-05-09 6:52 ` Santosh Y
2013-05-09 14:21 ` James Bottomley
2013-05-10 1:52 ` Seungwon Jeon [this message]
2013-05-08 8:41 ` [PATCH v4 2/6] scsi: ufs: amend interrupt configuration Seungwon Jeon
2013-05-08 15:19 ` Santosh Y
2013-05-08 8:41 ` [PATCH v4 3/6] scsi: ufs: fix interrupt status clears Seungwon Jeon
2013-05-08 15:19 ` Santosh Y
2013-05-08 8:42 ` [PATCH v4 4/6] scsi: ufs: rework link start-up process Seungwon Jeon
2013-05-08 15:20 ` Santosh Y
2013-05-08 8:42 ` [PATCH v4 5/6] scsi: ufs: add dme configuration primitives Seungwon Jeon
2013-05-09 6:53 ` Santosh Y
2013-05-08 8:43 ` [PATCH v4 6/6] scsi: ufs: add dme control primitives Seungwon Jeon
2013-05-09 6:53 ` Santosh Y
2013-05-10 10:42 ` [PATCH] scsi: ufs: use devres functions for ufshcd Seungwon Jeon
2013-05-10 11:00 ` Seungwon Jeon
2013-05-10 11:05 ` [PATCH resend] " Seungwon Jeon
2013-05-02 7:27 ` [PATCH 1/1] scsi: ufs: Add support for sending NOP OUT UPIU Santosh Y
2013-05-02 11:31 ` Sujit Reddy Thumma
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='000001ce4d21$0ac00920$20401b60$%jun@samsung.com' \
--to=tgih.jun@samsung.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=santoshsy@gmail.com \
--cc=vinholikatti@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