Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <20181023010707.153647-1-ryandcase@chromium.org>
In-Reply-To: <20181023010707.153647-1-ryandcase@chromium.org>
From:   Doug Anderson <dianders@chromium.org>
Date:   Mon, 5 Nov 2018 10:29:43 -0800
Message-ID: <CAD=FV=XGwyUEN3U-SzFB_VOLJ3LMcMttugKz7skgvMaBjt3H_w@mail.gmail.com>
Subject: Re: [PATCH v1] spi: spi-qcom-qspi: Fix remaining driver nits
To:     ryandcase@chromium.org, Mark Brown <broonie@kernel.org>
Cc:     linux-arm-msm <linux-arm-msm@vger.kernel.org>,
        Stephen Boyd <swboyd@chromium.org>,
        LKML <linux-kernel@vger.kernel.org>,
        linux-spi <linux-spi@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Mark,

On Mon, Oct 22, 2018 at 6:07 PM Ryan Case <ryandcase@chromium.org> wrote:
>
> Address remaining comments from original driver patch series
>
> * Move RD_FIFO_CFG to be ordered corretly
> * Expand spinlock comment
>
> Signed-off-by: Ryan Case <ryandcase@chromium.org>
> ---
>
>  drivers/spi/spi-qcom-qspi.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)

No huge deal (obviously) but I noticed that you landed a batch of
similar patches last night but didn't land this one.  Did it fall off
your radar or is there some other reason not to land it?

Thanks!

-Doug