Linux Renesas SOC kernel development
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: linux-renesas-soc@vger.kernel.org
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Wolfram Sang <wsa@the-dreams.de>
Subject: [PULL REQUEST] renesas/topic/i2c_sdhi_maintenance for renesas drivers
Date: Wed, 31 Aug 2016 08:58:38 +0200	[thread overview]
Message-ID: <20160831065835.GA7452@katana> (raw)

[-- Attachment #1: Type: text/plain, Size: 2054 bytes --]

Hi Geert,

here is a topic branch for renesas-drivers. Most of the patches I did
for this i2c/sdhi maintenance task are already in renesas-drivers,
because they came back via linux-next. Only the last three are missing
currently, but they are on the way, too. So, this branch will soonish
become obsolete again. Yay!

Kind regards,

   Wolfram


The following changes since commit 3eab887a55424fc2c27553b7bfe32330df83f7b8:

  Linux 4.8-rc4 (2016-08-28 15:04:33 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git renesas/topic/i2c_sdhi_maintenance

for you to fetch changes up to 91d6e42f0ba217c5d26d88648a18022f573d75de:

  ARM: shmobile: fix regulator quirk for Gen2 (2016-08-31 08:51:08 +0200)

----------------------------------------------------------------
Wolfram Sang (9):
      arm64: dts: r8a7795: set maximum frequency for SDHI clocks
      i2c: mux: demux-pinctrl: invalidate properly when switching fails
      i2c: sh_mobile: use proper device with dma_mapping_error
      i2c: rcar: use proper device with dma_mapping_error
      mmc: host: sh_mobile_sdhi: move card_busy from tmio to sdhi
      mmc: host: sh_mobile_sdhi: don't populate unneeded functions
      i2c: mux: demux-pinctrl: run properly with multiple instances
      Documentation: devicetree: changesets do locking on their own meanwhile
      ARM: shmobile: fix regulator quirk for Gen2

 Documentation/devicetree/changesets.txt            | 19 ++-----
 arch/arm/mach-shmobile/regulator-quirk-rcar-gen2.c | 62 +++++++++-------------
 arch/arm64/boot/dts/renesas/r8a7795.dtsi           |  4 ++
 drivers/i2c/busses/i2c-rcar.c                      |  2 +-
 drivers/i2c/busses/i2c-sh_mobile.c                 |  2 +-
 drivers/i2c/muxes/i2c-demux-pinctrl.c              | 15 ++++--
 drivers/mmc/host/sh_mobile_sdhi.c                  | 16 +++++-
 drivers/mmc/host/tmio_mmc.h                        |  1 +
 drivers/mmc/host/tmio_mmc_pio.c                    |  9 +---
 9 files changed, 65 insertions(+), 65 deletions(-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

                 reply	other threads:[~2016-08-31  6:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20160831065835.GA7452@katana \
    --to=wsa@the-dreams.de \
    --cc=geert@linux-m68k.org \
    --cc=linux-renesas-soc@vger.kernel.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