linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	linux-spi@vger.kernel.org
Subject: Re: [PATCH v3 0/2] Introduce Socionext F_OSPI SPI flash controller
Date: Thu, 24 Nov 2022 13:27:03 +0000	[thread overview]
Message-ID: <166929642318.251519.15577322648856458506.b4-ty@kernel.org> (raw)
In-Reply-To: <20221124003351.7792-1-hayashi.kunihiko@socionext.com>

On Thu, 24 Nov 2022 09:33:49 +0900, Kunihiko Hayashi wrote:
> This series adds dt-bindings and a driver for Socionext F_OSPI controller
> for connecting an SPI Flash memory over up to 8-bit wide bus.
> The controller supports up to 4 chip selects.
> 
> Changes since v2:
> - Drop a redundant word in the subject line
> - Drop quotes of referenceing URL in dt-bindings
> - Add Reviewed-by line to dt-bindings patch
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/2] dt-bindings: spi: Add Socionext F_OSPI controller
      commit: bcd58c8ca0f89fe6a890f909916bc97561341a06
[2/2] spi: Add Socionext F_OSPI SPI flash controller driver
      commit: 1b74dd64c8612619e399e5a31da79a3636914495

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark

      parent reply	other threads:[~2022-11-24 13:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-24  0:33 [PATCH v3 0/2] Introduce Socionext F_OSPI SPI flash controller Kunihiko Hayashi
2022-11-24  0:33 ` [PATCH v3 1/2] dt-bindings: spi: Add Socionext F_OSPI controller Kunihiko Hayashi
2022-11-24  0:33 ` [PATCH v3 2/2] spi: Add Socionext F_OSPI SPI flash controller driver Kunihiko Hayashi
2022-11-29 16:49   ` Geert Uytterhoeven
2022-11-30  0:47     ` Kunihiko Hayashi
2022-11-30  8:46       ` Geert Uytterhoeven
2022-11-24 13:27 ` Mark Brown [this message]

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=166929642318.251519.15577322648856458506.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hayashi.kunihiko@socionext.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=robh+dt@kernel.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).