From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Vivek Gautam <vivek.gautam@codeaurora.org>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
jejb@linux.vnet.ibm.com, evgreen@chromium.org,
linux-scsi@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Subhash Jadavani <subhashj@codeaurora.org>,
mka@chromium.org
Subject: Re: [PATCH 1/1] scsi/ufshcd: Fix NULL pointer dereference for in ufshcd_init
Date: Tue, 25 Sep 2018 21:05:03 -0400 [thread overview]
Message-ID: <yq1lg7pgjb4.fsf@oracle.com> (raw)
In-Reply-To: <CAFp+6iFVQKvWj7o+nmoJVhgQpOz2gZ_Eo+e8c8qdoc18waJ+zw@mail.gmail.com> (Vivek Gautam's message of "Tue, 25 Sep 2018 15:20:43 +0530")
Vivek,
>> > > Bjorn, Subhash,
>> > > I am not certain of some of these devfreq, and clk_scaling bits
>> > > that are moved as part of this patch. Please help in reviewing the
>> > > change in the light of these features, and related sequence should
>> > > be followed.
>> > > Thanks.
>> > >
>> >
>> > You're right, there is a lot of logic moving around here. I think this
>> > looks okay to me.
>> >
>> > Reviewed-by: Evan Green <evgreen@chromium.org>
>>
>> Thanks Evan.
>>
>> Best regards
>> Vivek
>
> Gentle ping. Will you please consider picking this patch for the
> merge?
I was waiting for some feedback from Bjorn or Subhash.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2018-09-26 1:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-07 17:47 [PATCH 1/1] scsi/ufshcd: Fix NULL pointer dereference for in ufshcd_init Vivek Gautam
2018-08-28 19:41 ` Evan Green
2018-08-29 8:20 ` Vivek Gautam
2018-09-25 9:50 ` Vivek Gautam
2018-09-26 1:05 ` Martin K. Petersen [this message]
2018-09-26 6:17 ` Vivek Gautam
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=yq1lg7pgjb4.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=bjorn.andersson@linaro.org \
--cc=evgreen@chromium.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mka@chromium.org \
--cc=subhashj@codeaurora.org \
--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