linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ryan Case <ryandcase@chromium.org>
To: rdunlap@infradead.org
Cc: Mark Brown <broonie@kernel.org>,
	Boris Brezillon <boris.brezillon@bootlin.com>,
	Stephen Boyd <swboyd@chromium.org>,
	Doug Anderson <dianders@chromium.org>,
	linux-arm-msm@vger.kernel.org,
	Girish Mahadevan <girishm@codeaurora.org>,
	linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org
Subject: Re: [PATCH v2 2/2] spi: Introduce new driver for Qualcomm QuadSPI controller
Date: Thu, 20 Sep 2018 16:47:59 -0700	[thread overview]
Message-ID: <CACjz--kKjm4PnXR8Zfe2BvDYDu4KQ=3nNWfXAPwz3o_JAOw5Vg@mail.gmail.com> (raw)
In-Reply-To: <3b7c090f-42ef-1b5d-0708-0b3b52d49302@infradead.org>

On Thu, Sep 20, 2018 at 3:46 PM Randy Dunlap <rdunlap@infradead.org> wrote:
> On 9/20/18 3:40 PM, Ryan Case wrote:
> > diff --git a/drivers/spi/Kconfig b/drivers/spi/Kconfig
> > index de03d67bcd2b..36922e12c3b0 100644
> > --- a/drivers/spi/Kconfig
> > +++ b/drivers/spi/Kconfig
> > @@ -549,6 +549,12 @@ config SPI_RSPI
> >       help
> >         SPI driver for Renesas RSPI and QSPI blocks.
> >
> > +config SPI_QCOM_QSPI
> > +     tristate "QTI QPSPI controller"
>
>         Is that       QPSPI correct?
>         This is the only place that QPSPI or PSPI is used in this patch.
>

Thanks Randy, that is a typo. I'll fix this in the next revision in a
day or two pending further feedback.

  reply	other threads:[~2018-09-20 23:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-20 22:40 [PATCH v2 1/2] dt-bindings: spi: Qualcomm Quad SPI(QSPI) documentation Ryan Case
2018-09-20 22:40 ` [PATCH v2 2/2] spi: Introduce new driver for Qualcomm QuadSPI controller Ryan Case
2018-09-20 22:46   ` Randy Dunlap
2018-09-20 23:47     ` Ryan Case [this message]
2018-09-21 16:31   ` Mark Brown
2018-09-21 17:30 ` [PATCH v2 1/2] dt-bindings: spi: Qualcomm Quad SPI(QSPI) documentation Stephen Boyd
2018-09-21 17:39   ` Mark Brown
2018-09-21 18:33     ` Trent Piepho
2018-09-21 17:40   ` Doug Anderson
2018-09-21 18:40     ` Stephen Boyd
2018-09-21 18:48       ` Doug Anderson
2018-09-21 18:51       ` Mark Brown
2018-09-23  3:45         ` Stephen Boyd
2018-09-24 17:13           ` Doug Anderson
2018-09-24 18:23             ` Trent Piepho
2018-09-25 16:02               ` Doug Anderson

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='CACjz--kKjm4PnXR8Zfe2BvDYDu4KQ=3nNWfXAPwz3o_JAOw5Vg@mail.gmail.com' \
    --to=ryandcase@chromium.org \
    --cc=boris.brezillon@bootlin.com \
    --cc=broonie@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-spi@vger.kernel.org \
    --cc=rdunlap@infradead.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).