public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: Charles Keepax <ckeepax@opensource.cirrus.com>,
	Richard Fitzgerald <rf@opensource.cirrus.com>,
	linux-kernel@vger.kernel.org, patches@opensource.cirrus.com
Subject: Re: [PATCH v1 2/4] mfd: arizona: Add missing entries SPI to device ID table
Date: Tue, 28 Sep 2021 09:05:37 +0100	[thread overview]
Message-ID: <YVLM0VxNGdH8AxQO@google.com> (raw)
In-Reply-To: <20210927105528.GA4199@sirena.org.uk>

On Mon, 27 Sep 2021, Mark Brown wrote:

> On Mon, Sep 27, 2021 at 10:27:54AM +0000, Charles Keepax wrote:
> 
> > Yeah we should really be having different lists for SPI and I2C
> > here I guess. I am happy to have a quick look at doing a patch
> > for that, unless you particularly want to fix it up?
> 
> I dropped the patch so please feel free to go ahead.

Just this one, or should I drop the set?

-- 
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2021-09-28  8:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-23 19:46 [PATCH v1 0/4] mfd: Ensure DT compatibles have SPI device IDs Mark Brown
2021-09-23 19:46 ` [PATCH v1 1/4] mfd: altr_a10sr: Add SPI device ID table Mark Brown
2021-09-23 19:46 ` [PATCH v1 2/4] mfd: arizona: Add missing entries SPI to " Mark Brown
2021-09-24  9:24   ` Richard Fitzgerald
2021-09-24 11:20     ` Mark Brown
2021-09-27 10:27       ` Charles Keepax
2021-09-27 10:55         ` Mark Brown
2021-09-28  8:05           ` Lee Jones [this message]
2021-09-28 10:01             ` Lee Jones
2021-09-23 19:46 ` [PATCH v1 3/4] mfd: cpcap: Add SPI " Mark Brown
2021-09-23 19:46 ` [PATCH v1 4/4] mfd: sprd: " Mark Brown

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=YVLM0VxNGdH8AxQO@google.com \
    --to=lee.jones@linaro.org \
    --cc=broonie@kernel.org \
    --cc=ckeepax@opensource.cirrus.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=rf@opensource.cirrus.com \
    /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