From: Lee Jones <lee.jones@linaro.org>
To: Tuowen Zhao <ztuowen@gmail.com>
Cc: linux-kernel@vger.kernel.org, andriy.shevchenko@linux.intel.com,
mika.westerberg@linux.intel.com, acelan.kao@canonical.com,
mcgrof@kernel.org, davem@davemloft.net
Subject: [GIT PULL] Immutable branch between MFD, Docs, Sparc and Lib Devres due for the v5.5 merge window
Date: Mon, 11 Nov 2019 08:43:13 +0000 [thread overview]
Message-ID: <20191111084313.GL18902@dell> (raw)
In-Reply-To: <20191016210629.1005086-1-ztuowen@gmail.com>
Enjoy!
The following changes since commit 54ecb8f7028c5eb3d740bb82b0f1d90f2df63c5c:
Linux 5.4-rc1 (2019-09-30 10:35:40 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git ib-mfd-doc-sparc-libdevres-v5.5
for you to fetch changes up to 7b8c4d73d7fe68f371d11b38a353134e1ffe199f:
docs: driver-model: add devm_ioremap_uc (2019-11-11 08:40:27 +0000)
----------------------------------------------------------------
Immutable branch between MFD, Docs, Sparc and Lib Devres due for the v5.5 merge window
----------------------------------------------------------------
Tuowen Zhao (4):
sparc64: implement ioremap_uc
lib: devres: add a helper function for ioremap_uc
mfd: intel-lpss: Use devm_ioremap_uc for MMIO
docs: driver-model: add devm_ioremap_uc
Documentation/driver-api/driver-model/devres.rst | 1 +
arch/sparc/include/asm/io_64.h | 1 +
drivers/mfd/intel-lpss.c | 2 +-
include/linux/io.h | 2 ++
lib/devres.c | 19 +++++++++++++++++++
5 files changed, 24 insertions(+), 1 deletion(-)
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2019-11-11 8:43 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 21:06 [PATCH v5 0/4] Fix MTRR bug for intel-lpss-pci Tuowen Zhao
2019-10-16 21:06 ` [PATCH v5 1/4] sparc64: implement ioremap_uc Tuowen Zhao
2019-10-16 21:20 ` David Miller
2019-10-28 20:46 ` Fwd: " Tuowen Zhao
2019-10-28 23:09 ` David Miller
2019-11-11 8:40 ` Fwd: " Lee Jones
2019-12-10 8:08 ` Geert Uytterhoeven
2019-10-16 21:06 ` [PATCH v5 2/4] lib: devres: add a helper function for ioremap_uc Tuowen Zhao
[not found] ` <20191017143144.9985421848@mail.kernel.org>
2019-10-17 17:49 ` Tuowen Zhao
2019-10-18 16:47 ` Sasha Levin
2019-12-04 15:51 ` Tuowen Zhao
2019-12-04 19:54 ` Andy Shevchenko
2019-12-04 20:06 ` Tuowen Zhao
2019-12-16 13:06 ` Greg KH
2019-12-16 18:02 ` Tuowen Zhao
2019-11-11 8:41 ` Lee Jones
2019-12-10 8:06 ` Geert Uytterhoeven
2019-12-10 12:50 ` Lee Jones
2019-10-16 21:06 ` [PATCH v5 3/4] mfd: intel-lpss: use devm_ioremap_uc for MMIO Tuowen Zhao
2019-10-22 19:01 ` Roman Gilg
2019-11-11 8:41 ` Lee Jones
2019-12-10 8:11 ` Geert Uytterhoeven
2019-10-16 21:06 ` [PATCH v5 4/4] docs: driver-model: add devm_ioremap_uc Tuowen Zhao
2019-10-23 11:26 ` Luis Chamberlain
2019-11-11 8:41 ` Lee Jones
2019-10-17 7:14 ` [PATCH v5 0/4] Fix MTRR bug for intel-lpss-pci Andy Shevchenko
2019-10-17 7:31 ` Lee Jones
2019-10-17 8:04 ` Andy Shevchenko
2019-10-17 8:22 ` Lee Jones
2019-10-17 9:52 ` Andy Shevchenko
2019-11-11 8:43 ` Lee Jones [this message]
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=20191111084313.GL18902@dell \
--to=lee.jones@linaro.org \
--cc=acelan.kao@canonical.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=ztuowen@gmail.com \
/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).