From: "Gilad Broner" <gbroner@codeaurora.org>
To: "Akinobu Mita" <akinobu.mita@gmail.com>
Cc: "Gilad Broner" <gbroner@codeaurora.org>,
"Jej B" <james.bottomley@hansenpartnership.com>,
"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>,
"Yaniv Gardi" <ygardi@codeaurora.org>,
"Dolev Raviv" <draviv@codeaurora.org>,
"Lee Susman" <lsusman@codeaurora.org>,
"Raviv Shvili" <rshvili@codeaurora.org>,
"Vinayak Holikatti" <vinholikatti@gmail.com>,
"James E.J. Bottomley" <jbottomley@parallels.com>
Subject: Re: [PATCH v3 2/4] scsi: ufs: add debugfs for ufs
Date: Sun, 1 Mar 2015 08:29:39 -0000 [thread overview]
Message-ID: <721fb67352e3cefe26a4fda6d2b289fe.squirrel@codeaurora.org> (raw)
In-Reply-To: <CAC5umygAXRyJmLPEFSTKKneicPZD4m=_RbkDfwQKoX3fvCP1Dw@mail.gmail.com>
>> +#define UFSHCD_UPDATE_TAG_STATS(hba, tag)
>> +#define UFSHCD_UPDATE_TAG_STATS_COMPLETION(hba, cmd)
>> +#define UFSHCD_UPDATE_ERROR_STATS(hba, type)
>> +
>> +#endif
>
> Is there any reason that these are defined as macros instead of
> static functions?
No special reason that I'm aware of. I will convert those to functions.
>> out_remove_scsi_host:
>> @@ -5769,6 +5969,7 @@ exit_gating:
>> out_disable:
>> hba->is_irq_enabled = false;
>> scsi_host_put(host);
>> + ufsdbg_remove_debugfs(hba);
>> ufshcd_hba_exit(hba);
>> out_error:
>> return err;
>
> This ufsdbg_remove_debugfs() call on error path of ufshcd_init() is
> unnecessary. Because ufsdbg_add_debugfs() is called at the last of
> ufshcd_init() and can't fail.
>
I will fix this in the next patchset.
--
Qualcomm Israel, on behalf of Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-03-01 8:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 8:08 [PATCH v3 0/4] Add ioctl and debug utilities to UFS driver Gilad Broner
2015-02-23 8:08 ` [PATCH v3 1/4] scsi: ufs: add ioctl interface for query request Gilad Broner
2015-02-23 9:16 ` Dov Levenglick
2015-02-23 8:08 ` [PATCH v3 2/4] scsi: ufs: add debugfs for ufs Gilad Broner
2015-02-23 9:15 ` Dov Levenglick
2015-02-24 15:10 ` Akinobu Mita
2015-03-01 8:29 ` Gilad Broner [this message]
2015-02-23 8:08 ` [PATCH v3 3/4] scsi: ufs: add trace events and dump prints for debug Gilad Broner
2015-02-23 9:15 ` Dov Levenglick
2015-02-23 11:51 ` Steven Rostedt
2015-02-23 17:12 ` Steven Rostedt
2015-03-01 8:33 ` Gilad Broner
2015-02-23 8:08 ` [PATCH v3 4/4] scsi: ufs: inject errors to verify error handling Gilad Broner
2015-02-23 9:10 ` Dov Levenglick
2015-02-23 9:10 ` [PATCH v3 0/4] Add ioctl and debug utilities to UFS driver Dov Levenglick
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=721fb67352e3cefe26a4fda6d2b289fe.squirrel@codeaurora.org \
--to=gbroner@codeaurora.org \
--cc=akinobu.mita@gmail.com \
--cc=draviv@codeaurora.org \
--cc=james.bottomley@hansenpartnership.com \
--cc=jbottomley@parallels.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=lsusman@codeaurora.org \
--cc=rshvili@codeaurora.org \
--cc=santoshsy@gmail.com \
--cc=subhashj@codeaurora.org \
--cc=vinholikatti@gmail.com \
--cc=ygardi@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