mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Hawkins, Nick" <nick.hawkins@hpe.com>, soc@kernel.org
Cc: "Guenter Roeck" <linux@roeck-us.net>,
	"Verdun, Jean-Marie" <verdun@hpe.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	krzysztof.kozlowski+dt@linaro.org,
	"Russell King" <linux@armlinux.org.uk>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5 2/2] ARM: multi_v7_defconfig: Add GXP Fan and SPI support
Date: Wed, 25 Jan 2023 09:25:25 +0100	[thread overview]
Message-ID: <3dabfe7f-1a15-4397-a360-ff048bc97a31@app.fastmail.com> (raw)
In-Reply-To: <20230113160651.51201-3-nick.hawkins@hpe.com>

On Fri, Jan 13, 2023, at 17:06, nick.hawkins@hpe.com wrote:
> From: Nick Hawkins <nick.hawkins@hpe.com>
>
> In order for HPE platforms to be supported by linux on GXP it is
> necessary for there to be fan and spi driver support. There fan driver
> can support up to 16 fans that are driven by pwm through the CPLD. The
> SPI driver supports access to the core flash and bios part. The SPI
> driver spi-gxp was added previously to linux.
>
> Signed-off-by: Nick Hawkins <nick.hawkins@hpe.com>
> Acked-by: Guenter Roeck <linux@roeck-us.net>
>

Applied to the soc/defconfig branch, but left the 1/2 for
now as I still had comments.

    ARnd

      reply	other threads:[~2023-01-25  8:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-13 16:06 [PATCH v5 0/2] ARM: Add GXP Fan and SPI controllers nick.hawkins
2023-01-13 16:06 ` [PATCH v5 1/2] ARM: dts: add GXP Support for fans and SPI nick.hawkins
2023-01-25  8:07   ` Arnd Bergmann
2023-01-26 18:47     ` Hawkins, Nick
2023-01-13 16:06 ` [PATCH v5 2/2] ARM: multi_v7_defconfig: Add GXP Fan and SPI support nick.hawkins
2023-01-25  8:25   ` Arnd Bergmann [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=3dabfe7f-1a15-4397-a360-ff048bc97a31@app.fastmail.com \
    --to=arnd@arndb.de \
    --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@armlinux.org.uk \
    --cc=linux@roeck-us.net \
    --cc=nick.hawkins@hpe.com \
    --cc=robh+dt@kernel.org \
    --cc=soc@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

all inboxes | Powered by JetHome®