From: valdis.kletnieks@vt.edu
To: Bart Van Assche <Bart.VanAssche@wdc.com>
Cc: "sayalil@codeaurora.org" <sayalil@codeaurora.org>,
"robh@kernel.org" <robh@kernel.org>,
"vinholikatti@gmail.com" <vinholikatti@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"asutoshd@codeaurora.org" <asutoshd@codeaurora.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"evgreen@chromium.org" <evgreen@chromium.org>,
"cang@codeaurora.org" <cang@codeaurora.org>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"subhashj@codeaurora.org" <subhashj@codeaurora.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"vivek.gautam@codeaurora.org" <vivek.gautam@codeaurora.org>,
"rnayak@codeaurora.org" <rnayak@codeaurora.org>,
"jejb@linux.vnet.ibm.com" <jejb@linux.vnet.ibm.com>,
"malat@debian.org" <malat@debian.org>
Subject: Re: [PATCH V2 1/3] scsi: ufs: set the device reference clock setting
Date: Fri, 15 Jun 2018 16:37:34 -0400 [thread overview]
Message-ID: <95985.1529095054@turing-police.cc.vt.edu> (raw)
In-Reply-To: <33eec86a35248e5b20f15bb568641b9affcc0a9b.camel@wdc.com>
[-- Attachment #1: Type: text/plain, Size: 570 bytes --]
Actually, it makes it easier to follow the conversation.
On Thu, 14 Jun 2018 13:35:08 -0000, Bart Van Assche said:
> On Thu, 2018-06-14 at 17:03 +0530, sayali wrote:
> > Comment inline.
>
> Hello Sayali,
>
> Please don't use inline replies. That makes it very hard to follow the
> conversation.
Actually, it makes it easier to follow the conversation.
> * If IMAP has been enabled on the Exchange server that you are using then
> that means that you can choose from the many open source e-mail clients
> that support IMAP.
Which of the two is easier to follow?
[-- Attachment #2: Type: application/pgp-signature, Size: 486 bytes --]
next prev parent reply other threads:[~2018-06-15 20:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1528455990-24572-1-git-send-email-sayalil@codeaurora.org>
2018-06-08 11:06 ` Sayali Lokhande
2018-06-08 12:01 ` Adrian Hunter
2018-06-12 19:26 ` Rob Herring
2018-06-14 11:33 ` sayali
2018-06-14 13:35 ` Bart Van Assche
2018-06-15 20:37 ` valdis.kletnieks [this message]
2018-06-15 20:42 ` Bart Van Assche
2018-06-15 20:53 ` valdis.kletnieks
2018-06-15 20:58 ` Bart Van Assche
2018-06-14 14:29 ` Rob Herring
2018-06-21 8:52 ` sayali
2018-07-03 18:04 ` Rob Herring
2018-07-04 13:36 ` Sayali Lokhande
2018-06-08 11:06 ` [PATCH V2 2/3] scsi: ufs: Add ufs provisioning support Sayali Lokhande
2018-06-08 11:06 ` [PATCH V2 3/3] scsi: ufs: Add sysfs support for ufs provision Sayali Lokhande
2018-06-09 7:24 ` Greg Kroah-Hartman
2018-06-14 11:52 ` sayali
2018-06-09 11:50 ` [RFC PATCH] scsi: ufs: dev_attr_ufs_provision can be static kbuild test robot
2018-06-09 11:50 ` [PATCH V2 3/3] scsi: ufs: Add sysfs support for ufs provision kbuild test robot
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=95985.1529095054@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=Bart.VanAssche@wdc.com \
--cc=asutoshd@codeaurora.org \
--cc=cang@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=evgreen@chromium.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=malat@debian.org \
--cc=mark.rutland@arm.com \
--cc=martin.petersen@oracle.com \
--cc=rnayak@codeaurora.org \
--cc=robh@kernel.org \
--cc=sayalil@codeaurora.org \
--cc=subhashj@codeaurora.org \
--cc=vinholikatti@gmail.com \
--cc=vivek.gautam@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
all inboxes | Powered by JetHome®