linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ygardi@codeaurora.org
To: Akinobu Mita <akinobu.mita@gmail.com>
Cc: Yaniv Gardi <ygardi@codeaurora.org>,
	Rob Herring <robherring2@gmail.com>,
	Jej B <james.bottomley@hansenpartnership.com>,
	Paul Bolle <pebolle@tiscali.nl>,
	Christoph Hellwig <hch@infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	linux-arm-msm@vger.kernel.org, Santosh Y <santoshsy@gmail.com>,
	linux-scsi-owner@vger.kernel.org,
	Subhash Jadavani <subhashj@codeaurora.org>,
	Gilad Broner <gbroner@codeaurora.org>,
	Dolev Raviv <draviv@codeaurora.org>,
	Vinayak Holikatti <vinholikatti@gmail.com>,
	"James E.J. Bottomley" <jbottomley@odin.com>
Subject: Re: [PATCH v2 6/8] scsi: ufs: make the UFS variant a platform device
Date: Fri, 21 Aug 2015 22:19:58 -0000	[thread overview]
Message-ID: <46812b2d9fe024d935063d634e9e8971.squirrel@www.codeaurora.org> (raw)
In-Reply-To: <CAC5umyjOQOzxutHyuWr+UFqA+AK88dOP9VHmt=FeWarQgVUq+g@mail.gmail.com>

> 2015-08-20 22:59 GMT+09:00 Yaniv Gardi <ygardi@codeaurora.org>:
>> @@ -1036,7 +1037,7 @@ void ufs_qcom_clk_scale_notify(struct ufs_hba
>> *hba)
>>   * The variant operations configure the necessary controller and PHY
>>   * handshake during initialization.
>>   */
>> -static const struct ufs_hba_variant_ops ufs_hba_qcom_vops = {
>> +static struct ufs_hba_variant_ops ufs_hba_qcom_vops = {
>
> It's better to keep const.  In order to do this, we also need to put
> const to 'vops' member in struct ufs_hba and the second argument of
> ufshcd_pltfrm_init().

Why do you think it would be better to keep the vops as a const and have
the vops member in struct ufs_hba be const ?
I would say it is better to have the vops as is, and let each variany
decidehow it should behave.


>
>> +static void ufs_qcom_shutdown(struct platform_device *pdev)
>> +{
>> +       ufshcd_shutdown((struct ufs_hba *)platform_get_drvdata(pdev));
>> +}
>
> We don't need this function anymore since we have
> ufshcd_pltfrm_shutdown() now.

ok, as this variant shutdown is doing the same as pltform shutdown' it can
go away.

>
>> -static void ufshcd_pltfrm_shutdown(struct platform_device *pdev)
>> +void ufshcd_pltfrm_shutdown(struct platform_device *pdev)
>>  {
>> -       ufshcd_shutdown((struct ufs_hba *)platform_get_drvdata(pdev));
>> +       ufshcd_shutdown((struct ufs_hba *)platform_get_drvdata(pdev));
>
> Whitespace is used as code indent.  There are same issues in
> this patch series, so I recommend running checkpatch.pl before
> sending patches.

> --
> 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
>

  reply	other threads:[~2015-08-21 22:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20 13:58 [PATCH v2 0/8] Fix error message and present UFS variant Yaniv Gardi
2015-08-20 13:58 ` [PATCH v2 1/8] phy: qcom-ufs: fix build error when the component is built as a module Yaniv Gardi
2015-08-20 13:58 ` [PATCH v2 2/8] scsi: ufs-qcom: fix compilation warning if compiled " Yaniv Gardi
2015-08-20 13:58 ` [PATCH v2 3/8] scsi: ufs-qcom: update configuration option of SCSI_UFS_QCOM component Yaniv Gardi
2015-08-20 13:59 ` [PATCH v2 4/8] add ufshcd_get_variant ufshcd_set_variant Yaniv Gardi
2015-08-20 13:59 ` [PATCH v2 5/8] scsi: ufs: creates wrapper functions for vops Yaniv Gardi
2015-08-20 13:59 ` [PATCH v2 6/8] scsi: ufs: make the UFS variant a platform device Yaniv Gardi
2015-08-20 23:43   ` Akinobu Mita
2015-08-21 22:19     ` ygardi [this message]
2015-08-23 21:06   ` Rob Herring
2015-08-24  8:32     ` ygardi
2015-08-20 13:59 ` [PATCH v2 7/8] scsi: ufs-qcom: add debug prints for test bus Yaniv Gardi
2015-08-20 23:42   ` Akinobu Mita
2015-08-21 22:23     ` ygardi
2015-08-22  2:56       ` Akinobu Mita
2015-08-22  3:07   ` Akinobu Mita
2015-08-23  8:54     ` ygardi
2015-08-20 13:59 ` [PATCH v2 8/8] scsi: ufs-qcom: add QUniPro hardware support and power optimizations Yaniv Gardi

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=46812b2d9fe024d935063d634e9e8971.squirrel@www.codeaurora.org \
    --to=ygardi@codeaurora.org \
    --cc=akinobu.mita@gmail.com \
    --cc=draviv@codeaurora.org \
    --cc=gbroner@codeaurora.org \
    --cc=hch@infradead.org \
    --cc=james.bottomley@hansenpartnership.com \
    --cc=jbottomley@odin.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi-owner@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    --cc=robherring2@gmail.com \
    --cc=santoshsy@gmail.com \
    --cc=subhashj@codeaurora.org \
    --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;
as well as URLs for NNTP newsgroup(s).