public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [PATCH  0/6] Basic SoC support for r8a7743/r8a7745
Date: Tue, 18 Jul 2017 16:30:23 +0100	[thread overview]
Message-ID: <1500391823.1935.111.camel@codethink.co.uk> (raw)
In-Reply-To: <1499851271-20037-1-git-send-email-biju.das@bp.renesas.com>

On Wed, 2017-07-12 at 10:21 +0100, Biju Das wrote:
> This series aims to add basic SoC support for  
> r8a7743/r8a7745. All the patches in this series
> are cherry-picked from the upstream kernel.
> 
> This series has been tested against linux-cip tag v4.4.75-cip6.

These all look good to me, so I've applied these to the linux-4.4.y-cip
branch.  Are you going to add more driver support (e.g. ravb, xhci-rcar)
and device tree sources?

Ben.

> Laurent Pinchart (1):
>   ARM: shmobile: Consolidate R8A7743 and R8A779[234] machine definitions
> 
> Sergei Shtylyov (5):
>   sh_eth: add R8A7743/5 support
>   DT: irqchip: renesas-irqc: document R8A7743/5 support
>   sh-sci: document R8A7743/5 support
>   ARM: shmobile: r8a7743: basic SoC support
>   ARM: shmobile: r8a7745: basic SoC support
> 
>  Documentation/devicetree/bindings/arm/shmobile.txt |  4 +++
>  .../bindings/interrupt-controller/renesas,irqc.txt |  4 ++-
>  Documentation/devicetree/bindings/net/sh_eth.txt   |  2 ++
>  .../bindings/serial/renesas,sci-serial.txt         |  8 ++++++
>  arch/arm/mach-shmobile/Kconfig                     |  8 ++++++
>  arch/arm/mach-shmobile/Makefile                    |  2 --
>  arch/arm/mach-shmobile/setup-r8a7793.c             | 33 ----------------------
>  arch/arm/mach-shmobile/setup-r8a7794.c             | 33 ----------------------
>  arch/arm/mach-shmobile/setup-rcar-gen2.c           | 33 ++++++++++++++++++++++
>  drivers/net/ethernet/renesas/Kconfig               |  2 +-
>  drivers/net/ethernet/renesas/sh_eth.c              |  2 ++
>  11 files changed, 61 insertions(+), 70 deletions(-)
>  delete mode 100644 arch/arm/mach-shmobile/setup-r8a7793.c
>  delete mode 100644 arch/arm/mach-shmobile/setup-r8a7794.c
> 

-- 
Ben Hutchings
Software Developer, Codethink Ltd.

  parent reply	other threads:[~2017-07-18 15:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-12  9:21 [cip-dev] [PATCH 0/6] Basic SoC support for r8a7743/r8a7745 Biju Das
2017-07-12  9:21 ` [cip-dev] [PATCH 1/6] sh_eth: add R8A7743/5 support Biju Das
2017-07-12  9:21 ` [cip-dev] [PATCH 2/6] DT: irqchip: renesas-irqc: document " Biju Das
2017-07-12  9:21 ` [cip-dev] [PATCH 3/6] sh-sci: " Biju Das
2017-07-12  9:21 ` [cip-dev] [PATCH 4/6] ARM: shmobile: r8a7743: basic SoC support Biju Das
2017-07-12  9:21 ` [cip-dev] [PATCH 5/6] ARM: shmobile: Consolidate R8A7743 and R8A779[234] machine definitions Biju Das
2017-07-12  9:21 ` [cip-dev] [PATCH 6/6] ARM: shmobile: r8a7745: basic SoC support Biju Das
2017-07-18 15:30 ` Ben Hutchings [this message]
2017-07-18 15:58   ` [cip-dev] [PATCH 0/6] Basic SoC support for r8a7743/r8a7745 Ben Hutchings
2017-07-19  8:24     ` Biju Das
2017-07-19 13:54       ` Ben Hutchings
2017-07-19 13:59         ` Biju Das
2017-07-19 14:23           ` Ben Hutchings

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=1500391823.1935.111.camel@codethink.co.uk \
    --to=ben.hutchings@codethink.co.uk \
    --cc=cip-dev@lists.cip-project.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