devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: dkota@codeaurora.org
To: Doug Anderson <dianders@chromium.org>
Cc: Stephen Boyd <swboyd@chromium.org>,
	Mark Brown <broonie@kernel.org>,
	Matthias Kaehlcke <mka@chromium.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-spi <linux-spi@vger.kernel.org>,
	Andy Gross <andy.gross@linaro.org>,
	David Brown <david.brown@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>,
	"open list:ARM/QUALCOMM SUPPORT" <linux-soc@vger.kernel.org>,
	devicetree@vger.kernel.org,
	Girish Mahadevan <girishm@codeaurora.org>,
	dkota@codeaurora.org
Subject: Re: [PATCH V3] spi: spi-geni-qcom: Add SPI driver support for GENI based QUP
Date: Fri, 07 Sep 2018 15:44:52 +0530	[thread overview]
Message-ID: <b87df0b445cacd3755280aa8a6b2c3cb@codeaurora.org> (raw)
In-Reply-To: <2493fc3fa3f6e5d2bcdde27cee1c33df@codeaurora.org>

> 
> When spi_alloc_master() fails you don't want spi_master_put().
Agree, will update it.

--Dilip

  reply	other threads:[~2018-09-07 10:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-24 10:42 [PATCH V3] spi: spi-geni-qcom: Add SPI driver support for GENI based QUP Dilip Kota
2018-08-25  5:21 ` kbuild test robot
2018-08-25  6:14 ` kbuild test robot
2018-08-29  0:25 ` Rob Herring
2018-08-29 11:19   ` dkota
2018-08-30  0:30     ` Rob Herring
2018-08-31  0:49 ` Stephen Boyd
2018-09-02  5:06 ` Doug Anderson
2018-09-07 10:00   ` dkota
2018-09-07 10:14     ` dkota [this message]
2018-09-07 16:19     ` Doug Anderson
2018-09-07 16:19     ` Doug Anderson
2018-09-10  3:57       ` dkota
2018-09-10 11:26         ` Mark Brown
2018-09-10 14:24           ` dkota

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=b87df0b445cacd3755280aa8a6b2c3cb@codeaurora.org \
    --to=dkota@codeaurora.org \
    --cc=andy.gross@linaro.org \
    --cc=broonie@kernel.org \
    --cc=david.brown@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=girishm@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-soc@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mka@chromium.org \
    --cc=robh+dt@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).