From: Wolfram Sang <wsa@the-dreams.de>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Wolfram Sang <wsa@sang-engineering.com>,
linux-i2c@vger.kernel.org
Subject: Re: linux-next: Tree for Dec 16 (i2c/busses/i2c-emev2)
Date: Wed, 16 Dec 2015 22:18:48 +0100 [thread overview]
Message-ID: <20151216211847.GA12629@katana> (raw)
In-Reply-To: <5671D210.5050306@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 487 bytes --]
On Wed, Dec 16, 2015 at 01:05:20PM -0800, Randy Dunlap wrote:
> On 12/15/15 21:43, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20151215:
> >
> > The drm-misc tree gained a conflict against Linus' tree.
> >
> > The i2c tree gained a build failure for which I applied a patch.
> >
> > The gpio tree gained a build failure so I used the version from
> > next-20151215.
> >
>
> on x86_64, when CONFIG_I2C_SLAVE is not enabled:
We are working on it...
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-12-16 21:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-16 5:43 linux-next: Tree for Dec 16 Stephen Rothwell
2015-12-16 19:28 ` linux-next: Tree for Dec 16 (gpu/drm/vc4) Randy Dunlap
2015-12-17 0:42 ` Eric Anholt
2015-12-17 0:42 ` Eric Anholt
2015-12-16 20:23 ` linux-next: Tree for Dec 16 (lib/842/842_decompress) Randy Dunlap
2015-12-18 14:32 ` Dan Streetman
2015-12-18 16:08 ` Randy Dunlap
2015-12-21 17:12 ` Dan Streetman
2015-12-21 17:52 ` [PATCH] crypto: 842 - remove WARN inside printk Dan Streetman
2015-12-23 10:25 ` Herbert Xu
2015-12-16 21:05 ` linux-next: Tree for Dec 16 (i2c/busses/i2c-emev2) Randy Dunlap
2015-12-16 21:18 ` Wolfram Sang [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=20151216211847.GA12629@katana \
--to=wsa@the-dreams.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=wsa@sang-engineering.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.