linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: horms+renesas@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Second Round of Renesas ARM Based SoC Defconfig Updates for v4.14
Date: Thu, 17 Aug 2017 11:49:22 +0200	[thread overview]
Message-ID: <cover.1502960320.git.horms+renesas@verge.net.au> (raw)

Hi Olof, Hi Kevin, Hi Arnd,

Please consider these second round of Renesas ARM based SoC defconfig updates for v4.14.

This pull request is based on the previous round of
such requests, tagged as renesas-defconfig-for-v4.14,
which you have already pulled.


The following changes since commit 52078ca712cd933844721aaa700b3bd85234841f:

  ARM: multi_v7_defconfig: Enable DMA for Renesas serial ports (2017-07-27 16:06:23 +0200)

are available in the git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-defconfig2-for-v4.14

for you to fetch changes up to 0736aad1290d61bc3668f20253e1e1997ad8b3c1:

  ARM: shmobile: Enable BQ32000 rtc in shmobile_defconfig (2017-08-09 11:03:26 +0200)

----------------------------------------------------------------
Second Round of Renesas ARM Based SoC Defconfig Updates for v4.14

* Enable BQ32000 rtc in shmobile_defconfig

  Biju Das says "The iWave RZ/G1M Q7 SOM supports RTC (TI BQ32000).  To
  increase hardware support enable the driver in the shmobile_defconfig
  multiplatform configuration."

----------------------------------------------------------------
Biju Das (1):
      ARM: shmobile: Enable BQ32000 rtc in shmobile_defconfig

 arch/arm/configs/shmobile_defconfig | 1 +
 1 file changed, 1 insertion(+)

             reply	other threads:[~2017-08-17  9:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-17  9:49 Simon Horman [this message]
2017-08-17  9:49 ` [PATCH] ARM: shmobile: Enable BQ32000 rtc in shmobile_defconfig Simon Horman
2017-08-18 20:27 ` [GIT PULL] Second Round of Renesas ARM Based SoC Defconfig Updates for v4.14 Arnd Bergmann

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=cover.1502960320.git.horms+renesas@verge.net.au \
    --to=horms+renesas@verge.net.au \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).