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.1
Date: Fri, 17 Apr 2015 10:33:54 +0200 [thread overview]
Message-ID: <20150417083349.GA1323@katana> (raw)
[-- Attachment #1: Type: text/plain, Size: 983 bytes --]
Linus,
here are two buildfixes for I2C based on your tree from the day before
yesterday. Sadly, these build errors never reached me while the patches
were sitting in -next. Need to fix that. Please pull.
Thanks,
Wolfram
The following changes since commit bb0fd7ab0986105765d11baa82e619c618a235aa:
Merge branch 'for-linus' of git://ftp.arm.linux.org.uk/~rmk/linux-arm (2015-04-14 21:03:26 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git i2c/for-next
for you to fetch changes up to c1c21f4e60ed4523292f1a89ff45a208bddd3849:
i2c: core: Export bus recovery functions (2015-04-15 21:02:07 +0200)
----------------------------------------------------------------
Guenter Roeck (1):
i2c: jz4780: Fix build for m68k and sparc64
Mark Brown (1):
i2c: core: Export bus recovery functions
drivers/i2c/busses/i2c-jz4780.c | 1 +
drivers/i2c/i2c-core.c | 3 +++
2 files changed, 4 insertions(+)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2015-04-17 8:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 8:33 Wolfram Sang [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-06-18 15:23 [PULL REQUEST] i2c for 4.1 Wolfram Sang
2015-06-05 1:28 Wolfram Sang
2015-04-26 12:40 Wolfram Sang
2015-04-14 21:22 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=20150417083349.GA1323@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).