linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 3/3] i.MX defconfig updates for 4.14
Date: Fri, 18 Aug 2017 15:53:40 +0800	[thread overview]
Message-ID: <1503042820-13043-3-git-send-email-shawnguo@kernel.org> (raw)
In-Reply-To: <1503042820-13043-1-git-send-email-shawnguo@kernel.org>

The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877:

  Linux v4.13-rc1 (2017-07-15 15:22:10 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-defconfig-4.14

for you to fetch changes up to b834bc1c52b8d4b5a525eec619ad547da8bc3517:

  ARM: imx_v6_v7_defconfig: Enable staging video4linux drivers (2017-07-25 16:42:51 +0800)

----------------------------------------------------------------
i.MX defconfig updates for 4.14:
 - Enable SPI_GPIO and GPIO_74X164 support which are useful for some
   boards like imx7d-sabresd.
 - Enable build of CODA video codec and staging video4linux drivers.

----------------------------------------------------------------
Fabio Estevam (3):
      ARM: imx_v6_v7_defconfig: Enable SPI_GPIO
      ARM: imx_v6_v7_defconfig: Enable GPIO_74X164
      ARM: imx_v6_v7_defconfig: Select the coda driver as module

Steve Longerbeam (1):
      ARM: imx_v6_v7_defconfig: Enable staging video4linux drivers

 arch/arm/configs/imx_v6_v7_defconfig | 15 ++++++++++++++-
 1 file changed, 14 insertions(+), 1 deletion(-)

  parent reply	other threads:[~2017-08-18  7:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-18  7:53 [GIT PULL 1/3] i.MX device tree updates for 4.14 Shawn Guo
2017-08-18  7:53 ` [GIT PULL 2/3] Freescale arm64 " Shawn Guo
2017-08-18 20:46   ` Arnd Bergmann
2017-08-18  7:53 ` Shawn Guo [this message]
2017-08-18 20:30   ` [GIT PULL 3/3] i.MX defconfig " Arnd Bergmann
2017-08-18 21:01 ` [GIT PULL 1/3] i.MX device tree " 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=1503042820-13043-3-git-send-email-shawnguo@kernel.org \
    --to=shawnguo@kernel.org \
    --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).