The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Janne Grunau <j@jannau.net>
Cc: Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Tudor Ambarus <tudor.ambarus@microchip.com>,
	linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
	Alyssa Rosenzweig <alyssa@rosenzweig.io>,
	asahi@lists.linux.dev, linux-kernel@vger.kernel.org,
	Hector Martin <marcan@marcan.st>, Kazuki <kazukih0205@gmail.com>
Subject: Re: [PATCH v2 0/3] SPI core CS delay fixes and additions
Date: Thu, 16 Feb 2023 15:55:52 +0000	[thread overview]
Message-ID: <Y+5SCAj4Vk8NLrW9@sirena.org.uk> (raw)
In-Reply-To: <20230216090411.GH17933@jannau.net>

[-- Attachment #1: Type: text/plain, Size: 208 bytes --]

On Thu, Feb 16, 2023 at 10:04:11AM +0100, Janne Grunau wrote:

> can we still get "spi: Use a 32-bit DT property for 
> spi-cs-setup-delay-ns" into 6.2?

I think I sent a pull request for this already.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2023-02-16 15:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-13 10:23 [PATCH v2 0/3] SPI core CS delay fixes and additions Hector Martin
2023-01-13 10:23 ` [PATCH v2 1/3] spi: Use a 32-bit DT property for spi-cs-setup-delay-ns Hector Martin
2023-01-13 10:23 ` [PATCH v2 2/3] spi: dt-bindings: Add hold/inactive CS delay peripheral properties Hector Martin
2023-01-13 10:23 ` [PATCH v2 3/3] spi: Parse hold/inactive CS delay values from the DT Hector Martin
2023-01-13 15:57 ` [PATCH v2 0/3] SPI core CS delay fixes and additions Mark Brown
2023-02-14 18:52   ` Kazuki
2023-02-16  9:04     ` Janne Grunau
2023-02-16 15:55       ` Mark Brown [this message]
2023-02-16 16:21         ` Janne Grunau
2023-02-16 16:25           ` 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=Y+5SCAj4Vk8NLrW9@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alyssa@rosenzweig.io \
    --cc=asahi@lists.linux.dev \
    --cc=devicetree@vger.kernel.org \
    --cc=j@jannau.net \
    --cc=kazukih0205@gmail.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=marcan@marcan.st \
    --cc=robh+dt@kernel.org \
    --cc=tudor.ambarus@microchip.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