From: alokc@codeaurora.org
To: swboyd@chromium.org, dianders@chromium.org,
Mark Brown <broonie@kernel.org>
Cc: linux-arm-msm@vger.kernel.org,
linux-arm-msm-owner@vger.kernel.org, linux-spi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] spi-geni-qcom: Cleanup nitpicks and simplify probe function
Date: Thu, 25 Oct 2018 22:23:04 +0530 [thread overview]
Message-ID: <b391e2df12e31be9ba5e48f197a86471@codeaurora.org> (raw)
In-Reply-To: <1540485629-5970-1-git-send-email-alokc@codeaurora.org>
On 2018-10-25 22:10, Alok Chauhan wrote:
> This patch series fixed the following:
> * nitpicks from the previous review
> (https://patchwork.kernel.org/patch/10624849/)
> * Cleanup probe function by re-arranging existing APIs to starting of
> function and hence avoiding one goto jump and remove few redundant
> variables.
>
> Alok Chauhan (2):
> spi: spi-geni-qcom: fix nitpicks
> spi: spi-geni-qcom: Simplify probe function
>
> drivers/spi/spi-geni-qcom.c | 64
> +++++++++++++++++++++------------------------
> 1 file changed, 30 insertions(+), 34 deletions(-)
Added more folks as some them got missed by get_maintainer.pl for this
patch.
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
Forum,a Linux Foundation Collaborative Project
prev parent reply other threads:[~2018-10-25 16:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1540485629-5970-1-git-send-email-alokc@codeaurora.org>
2018-10-25 16:40 ` [PATCH 1/2] spi: spi-geni-qcom: fix nitpicks Alok Chauhan
2018-10-25 20:00 ` Doug Anderson
2018-11-04 2:35 ` Stephen Boyd
2018-11-05 12:03 ` Applied "spi: spi-geni-qcom: fix nitpicks" to the spi tree Mark Brown
2018-10-25 16:40 ` [PATCH 2/2] spi: spi-geni-qcom: Simplify probe function Alok Chauhan
2018-10-25 20:06 ` Doug Anderson
2018-11-04 2:36 ` Stephen Boyd
2018-11-05 12:03 ` Applied "spi: spi-geni-qcom: Simplify probe function" to the spi tree Mark Brown
2018-10-25 16:53 ` alokc [this message]
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=b391e2df12e31be9ba5e48f197a86471@codeaurora.org \
--to=alokc@codeaurora.org \
--cc=broonie@kernel.org \
--cc=dianders@chromium.org \
--cc=linux-arm-msm-owner@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=swboyd@chromium.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;
as well as URLs for NNTP newsgroup(s).