From: "Hawkins, Nick" <nick.hawkins@hpe.com>
To: Mark Brown <broonie@kernel.org>
Cc: "broonie@kernel.org" <broonie@kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"Verdun, Jean-Marie" <verdun@hpe.com>,
"linux@armlinux.org.uk" <linux@armlinux.org.uk>,
"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"arnd@arndb.de" <arnd@arndb.de>
Subject: RE: [PATCH v6 3/5] ARM: dts: hpe: Add spi driver node
Date: Wed, 5 Oct 2022 20:33:05 +0000 [thread overview]
Message-ID: <DM4PR84MB19274B41DEE65D882D4C8F27885D9@DM4PR84MB1927.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20220728161459.7738-4-nick.hawkins@hpe.com>
Greetings all,
Was there a particular issue with this patch? I just realized that patches 1,2, and 5 were accepted but not 3 or 4.
Thanks,
-Nick Hawkins
next prev parent reply other threads:[~2022-10-05 20:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 16:14 [PATCH v6 0/5] Add SPI Driver to HPE GXP Architecture nick.hawkins
2022-07-28 16:14 ` [PATCH v6 1/5] spi: spi-gxp: Add support for HPE GXP SoCs nick.hawkins
2022-07-28 16:14 ` [PATCH v6 2/5] spi: dt-bindings: add documentation for hpe,gxp-spifi nick.hawkins
2022-07-28 16:14 ` [PATCH v6 3/5] ARM: dts: hpe: Add spi driver node nick.hawkins
2022-10-05 20:33 ` Hawkins, Nick [this message]
2022-10-05 21:00 ` Arnd Bergmann
2022-07-28 16:14 ` [PATCH v6 4/5] ARM: configs: multi_v7_defconfig: Enable HPE GXP SPI driver nick.hawkins
2022-07-28 16:14 ` [PATCH v6 5/5] MAINTAINERS: add spi support to GXP nick.hawkins
2022-07-29 19:23 ` (subset) [PATCH v6 0/5] Add SPI Driver to HPE GXP Architecture 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=DM4PR84MB19274B41DEE65D882D4C8F27885D9@DM4PR84MB1927.NAMPRD84.PROD.OUTLOOK.COM \
--to=nick.hawkins@hpe.com \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=robh+dt@kernel.org \
--cc=verdun@hpe.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;
as well as URLs for NNTP newsgroup(s).