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 v1 2/4] scsi: ufs: add debugfs for ufs
Date: Tue, 10 Feb 2015 14:05:10 -0000 [thread overview]
Message-ID: <d3435b8ff38fb890e22f4f3a5521d524.squirrel@codeaurora.org> (raw)
In-Reply-To: <CAC5umyiQYWLVn-=VyOw1cdiGdukFhh3uBTj78djb67pugYZu-w@mail.gmail.com>
> Should we append the index for unique directory
> name for each contoroller like "ufs0", "ufs1", ...?
I agree - uploaded patch V2 in which this is handled.
Thanks,
Gilad.
--
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-02-10 14:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-03 15:37 [PATCH v1 0/4] Add ioctl and debug utilities to UFS driver Gilad Broner
2015-02-03 15:37 ` [PATCH v1 1/4] scsi: ufs: add ioctl interface for query request Gilad Broner
2015-02-03 15:37 ` Gilad Broner
2015-02-03 15:37 ` [PATCH v1 2/4] scsi: ufs: add debugfs for ufs Gilad Broner
2015-02-06 14:42 ` Akinobu Mita
2015-02-10 14:05 ` Gilad Broner [this message]
2015-02-03 15:37 ` [PATCH v1 3/4] scsi: ufs: add trace events and dump prints for debug Gilad Broner
2015-02-03 16:53 ` Steven Rostedt
2015-02-04 14:00 ` Gilad Broner
2015-02-03 15:37 ` [PATCH v1 4/4] scsi: ufs: inject errors to verify error handling Gilad Broner
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=d3435b8ff38fb890e22f4f3a5521d524.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.