devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Paul Cercueil <paul@crapouillou.net>
Cc: "Rob Herring" <robh+dt@kernel.org>,
	周琰杰 <zhouyanjie@wanyeetech.com>,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org, list@opendingux.net
Subject: Re: [PATCH 0/8] Misc Ingenic patches
Date: Tue, 1 Jun 2021 11:49:23 +0200	[thread overview]
Message-ID: <20210601094923.GE6961@alpha.franken.de> (raw)
In-Reply-To: <20210530171802.23649-1-paul@crapouillou.net>

On Sun, May 30, 2021 at 06:17:54PM +0100, Paul Cercueil wrote:
> Hi Thomas,
> 
> Here is a set of misc patches that don't really have any relation
> between themselves. I just thought you'd prefer one patchset than eight
> individual patches :)

either way is good as long it has a common topic.

> 
> Paul Cercueil (8):
>   MIPS: mm: XBurst CPU requires sync after DMA
>   MIPS: boot: Support specifying UART port on Ingenic SoCs
>   MIPS: cpu-probe: Fix FPU detection on Ingenic JZ4760(B)
>   MIPS: Kconfig: ingenic: Ensure MACH_INGENIC_GENERIC selects all SoCs
>   MIPS: ingenic: Select CPU_SUPPORTS_CPUFREQ && MIPS_EXTERNAL_TIMER
>   MIPS: ingenic: jz4780: Fix I2C nodes to match DT doc
>   MIPS: ingenic: gcw0: Set codec to cap-less mode for FM radio
>   MIPS: ingenic: rs90: Add dedicated VRAM memory region
> 
>  arch/mips/Kconfig                      |  3 +++
>  arch/mips/Kconfig.debug                |  8 ++++++++
>  arch/mips/boot/compressed/uart-16550.c |  4 ++--
>  arch/mips/boot/dts/ingenic/gcw0.dts    |  5 ++---
>  arch/mips/boot/dts/ingenic/jz4780.dtsi | 10 +++++-----
>  arch/mips/boot/dts/ingenic/rs90.dts    | 14 ++++++++++++++
>  arch/mips/ingenic/Kconfig              |  2 ++
>  arch/mips/kernel/cpu-probe.c           |  5 +++++
>  arch/mips/mm/dma-noncoherent.c         |  1 +
>  9 files changed, 42 insertions(+), 10 deletions(-)

series applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

      parent reply	other threads:[~2021-06-01  9:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-30 17:17 [PATCH 0/8] Misc Ingenic patches Paul Cercueil
2021-05-30 17:17 ` [PATCH 1/8] MIPS: mm: XBurst CPU requires sync after DMA Paul Cercueil
2021-05-30 17:17 ` [PATCH 2/8] MIPS: boot: Support specifying UART port on Ingenic SoCs Paul Cercueil
2021-05-30 17:17 ` [PATCH 3/8] MIPS: cpu-probe: Fix FPU detection on Ingenic JZ4760(B) Paul Cercueil
2021-05-30 17:17 ` [PATCH 4/8] MIPS: Kconfig: ingenic: Ensure MACH_INGENIC_GENERIC selects all SoCs Paul Cercueil
2021-05-30 17:17 ` [PATCH 5/8] MIPS: ingenic: Select CPU_SUPPORTS_CPUFREQ && MIPS_EXTERNAL_TIMER Paul Cercueil
2021-05-30 17:18 ` [PATCH 6/8] MIPS: ingenic: jz4780: Fix I2C nodes to match DT doc Paul Cercueil
2021-05-30 17:18 ` [PATCH 7/8] MIPS: ingenic: gcw0: Set codec to cap-less mode for FM radio Paul Cercueil
2021-05-30 17:18 ` [PATCH 8/8] MIPS: ingenic: rs90: Add dedicated VRAM memory region Paul Cercueil
2021-06-01  9:49 ` Thomas Bogendoerfer [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=20210601094923.GE6961@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=list@opendingux.net \
    --cc=paul@crapouillou.net \
    --cc=robh+dt@kernel.org \
    --cc=zhouyanjie@wanyeetech.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).