From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: Linus Torvalds
<torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PULL REQUEST] i2c for 4.0
Date: Sat, 7 Mar 2015 19:14:54 +0100 [thread overview]
Message-ID: <20150307181449.GA3371@katana> (raw)
[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]
Linus,
here is a set of updates and bugfixes for the new designware-baytrail
driver. And a documentation bugfix.
Please pull.
Thanks,
Wolfram
The following changes since commit 13a7a6ac0a11197edcd0f756a035f472b42cdf8b:
Linux 4.0-rc2 (2015-03-03 09:04:59 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git i2c/for-current
for you to fetch changes up to 5d232112f94b0f3920dc4fec09688ef6cb5c09df:
i2c: imx: add required clocks property to binding (2015-03-07 01:13:00 +0100)
----------------------------------------------------------------
Andy Shevchenko (5):
i2c: designware-baytrail: describe magic numbers
i2c: designware-baytrail: fix typo in error path
i2c: designware-baytrail: fix sparse warnings
i2c: designware-baytrail: cross-check lock functions
i2c: designware-baytrail: baytrail_i2c_acquire() might sleep
Matt Porter (1):
i2c: imx: add required clocks property to binding
Documentation/devicetree/bindings/i2c/i2c-imx.txt | 1 +
drivers/i2c/busses/i2c-designware-baytrail.c | 40 ++++++++++++-----------
2 files changed, 22 insertions(+), 19 deletions(-)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2015-03-07 18:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-07 18:14 Wolfram Sang [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-03-12 16:26 [PULL REQUEST] i2c for 4.0 Wolfram Sang
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=20150307181449.GA3371@katana \
--to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.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).