All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [PATCH 5/8] pinctrl: renesas: r8a7795: Optimize pinctrl image size for R8A774E1
Date: Sun, 1 Nov 2020 12:31:40 +0100	[thread overview]
Message-ID: <8cf93e2b-2a38-cbab-22f1-030091594185@gmail.com> (raw)
In-Reply-To: <20201028103429.3051-6-biju.das.jz@bp.renesas.com>

On 10/28/20 11:34 AM, Biju Das wrote:
> This driver supports both RZ/G2H and R-Car H3 SoCs.
> Optimize pinctrl image size for RZ/G2H, when support for R-Car H3
> (R8A7795) is not enabled
> 
> Based on the similar patch on Linux.

Applied, thanks

  reply	other threads:[~2020-11-01 11:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-28 10:34 [PATCH 0/8] Pin control support for RZ/G2[HN] Biju Das
2020-10-28 10:34 ` [PATCH 1/8] pinctrl: renesas: r8a77965: Add R8A774B1 PFC support Biju Das
2020-11-01 11:31   ` Marek Vasut
2020-10-28 10:34 ` [PATCH 2/8] pinctrl: renesas: r8a77951: Add R8A774E1 " Biju Das
2020-11-01 11:31   ` Marek Vasut
2020-10-28 10:34 ` [PATCH 3/8] pinctrl: renesas: r8a7796: Optimize pinctrl image size for R8A774A1 Biju Das
2020-11-01 11:31   ` Marek Vasut
2020-11-01 18:58     ` Biju Das
2020-10-28 10:34 ` [PATCH 4/8] pinctrl: renesas: r8a77965: Optimize pinctrl image size for R8A774B1 Biju Das
2020-11-01 11:31   ` Marek Vasut
2020-10-28 10:34 ` [PATCH 5/8] pinctrl: renesas: r8a7795: Optimize pinctrl image size for R8A774E1 Biju Das
2020-11-01 11:31   ` Marek Vasut [this message]
2020-10-28 10:34 ` [PATCH RFC 6/8] pinctrl: renesas: r8a7796: Optimize pinctrl image size for R8A7796 Biju Das
2020-10-28 10:34 ` [PATCH RFC 7/8] pinctrl: renesas: r8a77965: Optimize pinctrl image size for R8A77965 Biju Das
2020-10-28 10:34 ` [PATCH RFC 8/8] pinctrl: renesas: r8a7795: Optimize pinctrl image size for R8A7795 Biju Das

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=8cf93e2b-2a38-cbab-22f1-030091594185@gmail.com \
    --to=marek.vasut@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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.