From: Janne Grunau <j@jannau.net>
To: Mark Brown <broonie@kernel.org>
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 17:21:07 +0100 [thread overview]
Message-ID: <20230216162107.GJ17933@jannau.net> (raw)
In-Reply-To: <Y+5SCAj4Vk8NLrW9@sirena.org.uk>
On 2023-02-16 15:55:52 +0000, Mark Brown wrote:
> 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.
I see today's "[GIT PULL] SPI updates for v6.2-rc8-abi"
https://lore.kernel.org/lkml/20230216131125.4A6FAC433D2@smtp.kernel.org/
but it was neither in "SPI fixes for v6.2-rc3" or "SPI fixes for
v6.2-rc7" or in Linus' tree as of today.
I think something went wrong with "[GIT PULL] SPI updates for
v6.2-rc8-abi". The message reads is if you intended to just send
"spi: Use a 32-bit DT property for spi-cs-setup-delay-ns" and not 62
commits.
Janne
next prev parent reply other threads:[~2023-02-16 16:21 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
2023-02-16 16:21 ` Janne Grunau [this message]
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=20230216162107.GJ17933@jannau.net \
--to=j@jannau.net \
--cc=alyssa@rosenzweig.io \
--cc=asahi@lists.linux.dev \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--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