From: Vinod Koul <vinod.koul@intel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
greg@kroah.com, linux-kernel@vger.kernel.org
Subject: Re: Staging clear up
Date: Wed, 09 Nov 2011 22:33:01 +0530 [thread overview]
Message-ID: <1320858181.32205.1087.camel@vkoul-udesk3> (raw)
In-Reply-To: <20111109165316.GB4016@opensource.wolfsonmicro.com>
On Wed, 2011-11-09 at 16:53 +0000, Mark Brown wrote:
> On Wed, Nov 09, 2011 at 10:17:41PM +0530, Vinod Koul wrote:
> > On Wed, 2011-11-09 at 16:42 +0000, Mark Brown wrote:
>
> > > Someone will need to fix the build breakage from peering at the headers
> > > from staging.
>
> > Not really. The current driver will not build unless you tweak the
> > Kconfig. It has clear depends rule, so build will not break.
>
> Well, if that's the case we may as well delete the ASoC driver too since
> it'll not be possible to build it :)
Okay how about this, I give you nice beer when you meet me next time :D
I will ensure it builds for you for 3.3
Offtopic: I am ready with v2 of compressed API, testing stuff out. If
you/Dimitris have stuff to add, please drop me a note. I didn't see any
update after I published the tree
--
~Vinod
next prev parent reply other threads:[~2011-11-09 17:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 21:16 Alan Cox
2011-11-08 21:48 ` Greg KH
2011-11-08 23:51 ` Alan Cox
2011-11-09 0:05 ` Greg KH
2011-11-09 12:13 ` Mark Brown
2011-11-09 16:00 ` Vinod Koul
2011-11-09 16:42 ` Mark Brown
2011-11-09 16:47 ` Vinod Koul
2011-11-09 16:53 ` Mark Brown
2011-11-09 17:03 ` Vinod Koul [this message]
2011-11-09 17:08 ` Mark Brown
2011-11-09 17:12 ` Vinod Koul
2011-11-10 9:49 ` Dimitris Papastamos
2011-11-09 16:55 ` Greg KH
2011-11-09 16:58 ` Mark Brown
2011-11-09 17:30 ` Alan Cox
2011-11-09 22:59 ` Mark Brown
2011-11-09 23:03 ` Alan Cox
2011-11-09 23:03 ` Mark Brown
2011-11-09 23:05 ` Alan Cox
2011-11-09 23:11 ` Mark Brown
2011-11-09 23:25 ` Alan Cox
2011-11-10 2:52 ` Vinod Koul
2011-11-10 8:54 ` Alan Cox
2011-11-27 1:30 ` Greg KH
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=1320858181.32205.1087.camel@vkoul-udesk3 \
--to=vinod.koul@intel.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®