All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Hammer Hsieh <hammerh0314@gmail.com>
Cc: u.kleine-koenig@pengutronix.de, lee.jones@linaro.org,
	robh+dt@kernel.org, linux-pwm@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	wells.lu@sunplus.com, hammer.hsieh@sunplus.com
Subject: Re: [PATCH v4 0/2] Add PWM driver for Suplus SP7021 SoC
Date: Fri, 22 Apr 2022 19:23:26 +0200	[thread overview]
Message-ID: <YmLkjriZCm+juYEP@orome> (raw)
In-Reply-To: <1647945781-10191-1-git-send-email-hammerh0314@gmail.com>

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

On Tue, Mar 22, 2022 at 06:42:59PM +0800, Hammer Hsieh wrote:
> This is a patch series for PWM driver for Suplus SP7021 SoC.
> 
> Sunplus SP7021 is an ARM Cortex A7 (4 cores) based SoC. It integrates
> many peripherals (ex: UART. I2C, SPI, SDIO, eMMC, USB, SD card and
> etc.) into a single chip. It is designed for industrial control.

I just noticed as I was trying to do test builds that ARCH_SUNPLUS
doesn't exist yet. Are there any plans to add those in the near future?

I can always use COMPILE_TEST to do test build, but I like to also do
proper builds because they sometimes flag things that COMPILE_TEST
misses (like this one).

Thierry

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

  parent reply	other threads:[~2022-04-22 17:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-22 10:42 [PATCH v4 0/2] Add PWM driver for Suplus SP7021 SoC Hammer Hsieh
2022-03-22 10:43 ` [PATCH v4 1/2] dt-bindings: pwm: Add bindings doc for Sunplus SoC SP7021 PWM Driver Hammer Hsieh
2022-03-23 15:58   ` Rob Herring
2022-03-22 10:43 ` [PATCH v4 2/2] pwm: sunplus-pwm: Add " Hammer Hsieh
2022-04-22 16:36 ` [PATCH v4 0/2] Add PWM driver for Suplus SP7021 SoC Thierry Reding
2022-04-22 17:23 ` Thierry Reding [this message]
2022-04-25  1:49   ` hammer hsieh

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=YmLkjriZCm+juYEP@orome \
    --to=thierry.reding@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hammer.hsieh@sunplus.com \
    --cc=hammerh0314@gmail.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=u.kleine-koenig@pengutronix.de \
    --cc=wells.lu@sunplus.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.