From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
alsa-devel@alsa-project.org, linux-next@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: linux-next: Tree for April 4 (sound/soc)
Date: Tue, 5 Apr 2011 07:37:45 +0900 [thread overview]
Message-ID: <20110404223744.GA4609@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20110404083747.34ed1398.randy.dunlap@oracle.com>
On Mon, Apr 04, 2011 at 08:37:47AM -0700, Randy Dunlap wrote:
> On Mon, 4 Apr 2011 14:35:46 +1000 Stephen Rothwell wrote:
>
> > Hi all,
> >
> > Changes since 20110401:
>
>
> When CONFIG_SPI=n, CONFIG_I2C=n:
A patch was sent for this the other day, just waiting for review.
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Liam Girdwood <lrg@slimlogic.co.uk>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
alsa-devel@alsa-project.org
Subject: Re: linux-next: Tree for April 4 (sound/soc)
Date: Tue, 5 Apr 2011 07:37:45 +0900 [thread overview]
Message-ID: <20110404223744.GA4609@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20110404083747.34ed1398.randy.dunlap@oracle.com>
On Mon, Apr 04, 2011 at 08:37:47AM -0700, Randy Dunlap wrote:
> On Mon, 4 Apr 2011 14:35:46 +1000 Stephen Rothwell wrote:
>
> > Hi all,
> >
> > Changes since 20110401:
>
>
> When CONFIG_SPI=n, CONFIG_I2C=n:
A patch was sent for this the other day, just waiting for review.
next prev parent reply other threads:[~2011-04-04 22:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 4:35 linux-next: Tree for April 4 Stephen Rothwell
2011-04-04 15:37 ` linux-next: Tree for April 4 (sound/soc) Randy Dunlap
2011-04-04 16:05 ` 高万龙
2011-04-04 16:12 ` Randy Dunlap
2011-04-04 16:12 ` Randy Dunlap
2011-04-04 22:37 ` Mark Brown [this message]
2011-04-04 22:37 ` Mark Brown
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=20110404223744.GA4609@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
/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.